« Changelog History


meteor v1.3.2 Release Notes

Release Date: 2016-04-15 // about 8 years ago

    • The meteor/meteor repository now includes a Roadmap.md file: https://github.com/meteor/meteor/blob/devel/Roadmap.md

    • 🚀 Running npm install in bundle/programs/server when deploying an app also rebuilds any binary npm dependencies, fixing #6537. Set METEOR_SKIP_NPM_REBUILD=1 to disable this behavior if necessary.

    • Non-.js(on) files in node_modules (such as .less and .scss) are now processed by compiler plugins and may be imported by JS. #6037

    • 📦 The jquery package can now be completely removed from any app (#6563), and uses <app>/node_modules/jquery if available (#6626).

    • Source maps are once again generated for all bundled JS files, even if they are merely identity mappings, so that the files appear distinct in the browser, and stack traces make more sense. #6639

    • All application files in imports directories are now considered lazy, regardless of whether the app is using the modules package. This could be a breaking change for 1.3.2 apps that do not use modules or ecmascript but contain imports directories. Workaround: move files out of imports, or rename imports to something else.

    • ⬆️ The npm-bcrypt package has been upgraded to use the latest version (0.8.5) of the bcrypt npm package.

    • 🔌 Compiler plugins can call addJavaScript({ path }) multiple times with different paths for the same source file, and module.id will reflect this path instead of the source path, if they are different. #6806

    • 🛠 Fixed bugs: https://github.com/meteor/meteor/milestones/Release%201.3.2

    • 🛠 Fixed unintended change to Match.Optional which caused it to behave the same as the new Match.Maybe and incorrectly matching null where it previously would not have allowed it. #6735