Migrating to Meteor 1.8.2
Most of the new features in Meteor 1.8.2 are either applied directly behind the scenes (in a backwards compatible manner) or are opt-in. For a complete breakdown of the changes, please refer to the changelog.
The above being said, there are required migration steps that you should perform for this release to run smoothly.
Update the `@babel/runtime`
Be sure to update the
@babel/runtime npm package to its latest version
meteor npm install @babel/runtime@latest
Meteor Node Stubs
New Meteor applications now depend on
firstname.lastname@example.org, so it
may be a good idea to update to the same major version:
meteor npm install meteor-node-stubs@next
Packages should be re-published
If you are the author of any Meteor packages, and you encounter errors
when using those packages in a Meteor 1.8.2 application (for example,
module.watch being undefined), we recommend that you bump the minor
version of your package and republish it using Meteor 1.8.2, so
Meteor 1.8.2 applications will automatically use the new version of the
package, as compiled by Meteor 1.8.2:
cd path/to/your/package # Add api.versionsFrom("1.8.2") to Package.onUse in package.js... meteor --release 1.8.2 publish
This may not be necessary for all packages, especially those that have
been recently republished using Meteor 1.8.1, or local packages in the
packages/ directory (which are always recompiled from source).
However, republishing packages is a general solution to a wide variety
of package versioning and compilation problems, and package authors can
make their users’ lives easier by handling these issues proactively.
Migrating from a version older than 1.8?
If you’re migrating from a version of Meteor older than Meteor 1.8, there may be important considerations not listed in this guide (which specifically covers 1.8 to 1.8.2). Please review the older migration guides for details: