When thinking about Meteor&#x27;s value proposition, it&#x27;s been neck and neck between what you&#x27;re saying (which is that of a &quot;universal build tool&quot;) vs. it&#x27;s full stack reactive subscription capabilities. Both of which have been Meteor&#x27;s 2 most important features.<p>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&#x27;s a lot less work than it used to be using plain NPM, and you now have a lot more customization than in Meteor.<p>That&#x27;s why doubling down and continuing the thought of full stack reactivity is so important to Meteor. I&#x27;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.<p>If interested, here&#x27;s my take my take on what &quot;Reactive GraphQL&quot; means to Meteor developers:<p><a href="https:&#x2F;&#x2F;medium.com&#x2F;@faceyspacey&#x2F;what-reactive-graphql-means-for-meteor-3be285bce0b6" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;@faceyspacey&#x2F;what-reactive-graphql-means-...</a>