JSPM might be ready now but when I tried it, it really didn’t work very well. I think this will eventually overtake webpack because of the simplicity… although it still doesn’t take care of things that Grunt/Gulp/Webpack does like CSS, image processing, etc…
[quote="funkyeah, post:5, topic:13973, full:true"]
So beyond the learning curve, what, if any are the downsides? and/or why wouldn't MDG transition to adding a thin layer to Webpack to create their build system rather then maintained a custom one.... much like they now plan to do for Blaze on top of React?
Webpack can be as simple as a 5 line config file but it can quickly become complex. It can handle almost any situation with more configs but that makes things hard to learn and figure out. The other con is that it doesn’t compile CSS separately… they have their own method of requiring CSS at the JS module level, so you may need to compile CSS separately if that doesn’t align with your project.
If you read the writing on the wall, MDG is going to be using webpack for their new build system for ES6 modules. They really don’t have time to re-invent the wheel and make their own webpack. They could also claim that Meteor is ‘the easiest way to use webpack’ and would be a huge selling point.
This would give them a ton of hooks for their build tool, hot code patching, ES6 modules, hot patching on the react component level (via babel transforms) if React was used.