[faceyspacey]

When thinking about Meteor's value proposition, it's been neck and neck between what you're saying (which is that of a "universal build tool") vs. it's full stack reactive subscription capabilities. Both of which have been Meteor's 2 most important features.

That said, on the build side of things Webpack and Babel have been giving Meteor a run for its money. It takes more work to build your app with those tools, but it's a lot less work than it used to be using plain NPM, and you now have a lot more customization than in Meteor.

That's why doubling down and continuing the thought of full stack reactivity is so important to Meteor. I'm so glad to hear that they have suited up to upgrade their reactive server-side parts. I hope they put a lot of resources behind it.

If interested, here's my take my take on what "Reactive GraphQL" means to Meteor developers:

https://medium.com/@faceyspacey/what-reactive-graphql-means-...