Re:What's New in Webpack 2
by darkmagnus on Tuesday February 02, 2016 @06:51AM
(#11018894)
Any chance you can go into detail how you bundle your 3rd party dependencies separately? I have tried that, without much luck.
Re:What's New in Webpack 2
by true_religion on Tuesday February 02, 2016 @10:05AM
(#11019807)
For me it's like this:
> jspm bundle app//* - [app//*] js/tmp/dependency-bundle.js --inject --no-runtime
That tells JSPM to bundle everything except your application if your app lives within the app/ directory.
> jspm bundle babel js/tmp/bundles/babel.js --inject --skip-source-maps --minify
This tells it to bundle the Babel dependencies which aren't considered in the above.
Using bundle arythmetic.
jspm bundle src/app.js - src/[/*]
This will tell jspm to bundle src/app.js with all its dependencies, excluding everything in the src/ directory. This will result in JSPM bundling only your dependencies.
We do the same in our project: we bundle all the 3rd party libs when they change, so only our own code gets retranspiled on each page load. During deployment, we bundle all the JS in a single bundle (which is good for us, as we don't have too much JS in that project).