check out meteor-with-webpack

[gadicc]

@trusktr:

Just clone and cd meteor && meteor. I'm like half way, but currently you'll see three packages in the app's packages folder. The two lib ones depend on the webpack one. Each one has an entry point 'main.js' which gets transformed by the webpack package into a self-executing bundle.

Next I've gotta handle common npm dependencies across packages, allow a packages to have a config file so devs can specify multiple entry point files, and handle application code besides packages. That'll be the whole proof of concept. Then after that I'll get famous-views using it, pulling famous from npm instead of Atmosphere, but still depending on the other Atmosphere packages.

http://github.com/trusktr/meteor-with-webpack

[trusktr]

I started a new repo specifically for the webpack package, and will call it rocket:module on Atmosphere, not referring to webpack so that the underlying tech can be interchangeable. https://github.com/trusktr/rocket-module

[trusktr]

I'm aiming to finish the initial feature set by this Sunday, then make current famous-views work with it.