I get why it’s nice to not have to worry about the build process when getting started, or for your hackathon project. But when you get serious, the trade off is different.
It looks like Webpack is winning in the broader node / React ecosystem. So I was wondering what are the core reasons (other than legacy reasons) Meteor should handle the build process, and MDG should spend ressources on it, vs letting some other package that is excellent at just that do the job.
I’ve recently played with webpack:webpack. While it opens really really cool perspectives, it still feels like a mixed result coming from a hybrid approach to what build process should be like.
Over the last months, Meteor has done an ok job at following on the latest node / js trends (with imports in 1.3, .babelrc support etc) but it still looks like:
- work is getting duplicated with Meteor redoing what is already done on the node ecosystem
- Meteor updates are lagging, and there’s no easy way for you to get the latest build options you’d want to within Meteor.
So I was wondering
- what are people thoughts on that, what are the happy/painful experience with how things currently are.
- if we should except to see a change that would embrace an external proven tool, as we’ve seen with React gaining traction over Blaze within Meteor community