All-package structure for Meteor 1.3 and imports


#1

Hey guys,

I am wondering if you guys have succesfully converted the all-package structure to a simple file structure based on imports and exports.
A simple use case is a app with client/lib/server code and then a webview with the same lib/server code but a different client code.

app
|- mobile
| |-- client
| |-- lib
| |-- server
|
|- web
| |-- client
| |-- lib (imported from mobile/lib)
| |-- server (imported from mobile/server)

Is this as easy as using import '/mobile/lib' inside the web folder?

Or do I need to do more things? I’ve read about meteor-remote-autoupdate etc.

Greetings,
Lars