After some slight hiccups with 1.3.2 and 220.127.116.11, I’m happy to let you know that Meteor 18.104.22.168 is now a recommended release! You can begin using 22.214.171.124 by running
meteor update in any app directory.
Changes since v1.3.1:
- Fixed bugs #6819 and #6831.
- Fixed faulty comparison of
.targetPathproperties of files scanned by the
ImportScanner, which caused problems for apps using the
meteor/meteorrepository now includes a
bundle/programs/serverwhen deploying an app also rebuilds any binary npm dependencies, fixing #6537. Set
METEOR_SKIP_NPM_REBUILD=1to disable this behavior if necessary.
.scss) are now processed by compiler plugins and may be imported by JS. #6037
jquerypackage can now be completely removed from any app (#6563), and uses
<app>/node_modules/jqueryif 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
importsdirectories are now considered lazy, regardless of whether the app is using the
modulespackage. This could be a breaking change for 1.3.2 apps that do not use
importsdirectories. Workaround: move files out of
imports, or rename
importsto something else.
npm-bcryptpackage has been upgraded to use the latest version (0.8.5) of the
Match.Optionalonly passes if the value is
nullor the specified type, whereas previously it accepted
Compiler plugins can call
module.idwill reflect this
pathinstead of the source path, if they are different. #6806