Meteor v1.3.5 Release Notes

Release Date: 2016-07-16 // over 7 years ago
    • ๐Ÿ“ฆ Failed Meteor package downloads are now automatically resumed from the point of failure, up to ten times, with a five-second delay between attempts. #7399

    • ๐Ÿ“ฆ If an app has no package.json file, all packages in node_modules will be built into the production bundle. In other words, make sure you have a package.json file if you want to benefit from devDependencies pruning. 7b2193188fc9e297eefc841ce6035825164f0684

    • ๐Ÿ”Œ Binary npm dependencies of compiler plugins are now automatically rebuilt when Node/V8 versions change. #7297

    • Because .meteor/local is where purely local information should be stored, the .meteor/dev_bundle link has been renamed to .meteor/local/dev_bundle.

    • The .meteor/local/dev_bundle link now corresponds exactly to .meteor/release even when an app is using an older version of Meteor. d732c2e649794f350238d515153f7fb71969c526

    • ๐Ÿ“ฆ When recompiling binary npm packages, the npm rebuild command now receives the flags --update-binary and --no-bin-links, in addition to respecting the $METEOR_NPM_REBUILD_FLAGS environment variable. #7401

    • ๐Ÿ“ฆ The last solution found by the package version constraint solver is now stored in .meteor/local/resolver-result-cache.json so that it need not be recomputed every time Meteor starts up.

    • If the $GYP_MSVS_VERSION environment variable is not explicitly provided to meteor {node,npm}, the node-gyp tool will infer the appropriate version (though it still defaults to "2015").