Though Meteor 1.3 was released only a week ago, we’re shifting into a regime of doing smaller releases more often, as long as there’s stuff to fix (and there’s always stuff to fix).
In that spirit, I’m happy to announce the immediate availability of Meteor 1.3.1. To update to the new release, run
meteor update --release 1.3.1 in an app directory.
This release is not yet “recommended,” meaning we don’t yet print a banner in the console urging you to update. If there are no unexpected problems with the release, we will probably recommend it in the next week or so.
The changes are relatively conservative, but if you spot something here that’s been giving you trouble, then 1.3.1 might be the cure for your woes!
node_modulespaths have been shortened, fixing upgrade problems on Windows. #6609
Version 1.3.1 of Meteor can now publish packages for earlier versions of Meteor, provided those packages do not rely on
modules. #6484 #6618
meteor-babelnpm package used by
babel-compilerhas been upgraded to version 0.8.4.
meteor npmcommands now return the same exit codes as their child processes. #6673 #6675 (Thanks to @abernix for submitting a PR to fix this!)
Missing module warnings are no longer printed for Meteor packages, or for
requireis not a free variable, fixing https://github.com/practicalmeteor/meteor-mocha/issues/19.
Cordova iOS builds are no longer built by Meteor, but merely prepared for building.
Compiler plugin errors were formerly silenced for files not explicitly added in package.js. Now those errors are reported when/if the files are imported by the