The change begins this week with the release of Meteor 1.3, which supports a module system that integrates with Node.js and NPM to enable better testing. The full switch to NPM will happen later in 2016, along with decoupling of some core packages.
For version 1.3, the modules help with testing. “Unit testing is more effective when your code is divided into clear units, and that’s one reason why Meteor 1.3 supports a standards-compliant module system,” said Zoltan Olah, head of customer success at Meteor. The NPM integration enables developers to install client and server packages into applications, including React and Angular components.
As a major release, Meteor 1.3 will help teams with production applications to manage, scale, and test Meteor code bases. New testing capabilities eliminate a need to break up an application into multiple local packages for testing.
Also planned for a future release of Meteor are updates for Node, to version 4, and MongoDB, to version 3.2. Additionally, Meteor’s Livedata system now supports tunable queries to help scale large apps.
Meteor is publishing an up-to-date Meteor Guide with the release, featuring best practices.