Changelog History
Page 12
-
v1.6.1.2 Changes
May 28, 2018 -
v1.6.1.1 Changes
April 02, 2018💥 Breaking changes
N/A
Migration Steps
- ⚡️ Update
@babel/runtime
npm package and any custom Babel plugin enabled in.babelrc
sh meteor npm install @babel/[email protected]
🔄 Changes
⚡️ Node has been updated to version 8.11.1, an important security release, with a critical patch applied to solve a segmentation fault problem that was introduced in Node 8.10.0.
⚡️ The
meteor-babel
npm package has been updated to version 7.0.0-beta.42, which may require updating any custom Babel plugins you've enabled in a.babelrc
file, and/or running the following command to update@babel/runtime
:meteor npm install @babel/[email protected]
- ⚡️ Update
-
v1.6 Changes
October 30, 2017- 📦 Important note for package maintainers:
With the jump to Node 8, some packages published using Meteor 1.6 may no longer be compatible with older Meteor versions. In order to maintain compatibility with Meteor 1.5 apps when publishing your package, you can specify a release version with the meteor publish command:
meteor --release 1.5.3 publish
If you're interested in taking advantage of Meteor 1.6 while still supporting older Meteor versions, you can consider publishing for Meteor 1.6 from a new branch, with your package's minor or major version bumped. You can then continue to publish for Meteor 1.5 from the original branch. Note that the 1.6 branch version bump is important so that you can continue publishing patch updates for Meteor 1.5 from the original branch.
⬆️ Node.js has been upgraded to version 8.8.1, which will be entering long-term support (LTS) coverage on 31 October 2017, lasting through December 2019 (full schedule). This is a major upgrade from the previous version of Node.js used by Meteor, 4.8.4.
⬆️ The
npm
npm package has been upgraded to version 5.4.2, a major upgrade from 4.6.1. While this update should be backwards-compatible for existing Meteor apps and packages, if you are the maintainer of any Meteor packages, pay close attention to yournpm-shrinkwrap.json
files when first using this version ofnpm
. For normal Meteor application development, this upgrade primarily affects the version ofnpm
used bymeteor npm ...
commands. A functional installation ofgit
may be required to support GitHub repository and/or tarball URLs. Troubleshooting. PR #8835In addition to
meteor node
andmeteor npm
, which are convenient shorthands fornode
andnpm
,meteor npx <command>
can be used to execute commands from a localnode_modules/.bin
directory or from thenpm
cache. Any packages necessary to run the command will be automatically downloaded. Read about it, or just try some commands:meteor npx cowsay mooooo meteor npx uuid meteor npx nyancat meteor npx yarn
The
meteor debug
command has been superseded by the more flexible--inspect
and--inspect-brk
command-line flags, which work for anyrun
,test
, ortest-packages
command.
The syntax of these flags is the same as the equivalent Node.js flags, with two notable differences:
The flags affect the server process spawned by the build process, rather than affecting the build process itself.
The
--inspect-brk
flag causes the server process to pause just after server code has loaded but before it begins to execute, giving the developer a chance to set breakpoints in server code.
🏁 On Windows, Meteor can now be installed or reinstalled from scratch using the command
choco install meteor
, using the Chocolatey package manager. This method of installation replaces the oldInstallMeteor.exe
installer, which had a number of shortcomings, and will no longer be supported.🏁 Fresh installs of Meteor 1.6 on 64-bit Windows machines will now use native 64-bit Node.js binaries, rather than a 32-bit version of Node.js. In addition to being faster, native 64-bit support will enable Windows developers to debug asynchronous stack traces more easily in the new Node.js inspector, which is only fully supported by native 64-bit architectures. Note that merely running
meteor update
from a 32-bit version of Meteor will still install a 32-bit version of Meteor 1.6, so you should usechoco install meteor
to get a fresh 64-bit version. PR #9218👍 To support developers running on a 32-bit OS, Meteor now supports both 32- and 64-bit versions of Mongo. Mongo 3.2 is the last 32-bit version available from Mongo. Meteor running on a 32-bit OS will use a 32-bit version of Mongo 3.2 and 64-bit platforms will receive newer Mongo versions in future releases. PR #9173
After several reliability improvements, native file watching has been un-disabled on Windows. Though native file change notifications will probably never work with network or shared virtual file systems (e.g., NTFS or Vagrant-mounted disks), Meteor uses an efficient prioritized polling system as a fallback for those file systems.
Various optimizations have reduced the on-disk size of the
meteor-tool
package from 545MB (1.5.2.2) to 219MB.⬆️ The
meteor-babel
package has been upgraded to version 0.24.6, to take better advantage of native language features in Node 8.⬆️ The
reify
npm package has been upgraded to version 0.12.3.⬆️ The
meteor-promise
package has been upgraded to version 0.8.6, to enable better handling ofUnhandledPromiseRejectionWarning
s.⬆️ The
node-gyp
npm package has been upgraded to version 3.6.2.⚡️ The
node-pre-gyp
npm package has been updated to version 0.6.36.⬆️ The
fibers
npm package has been upgraded to version 2.0.0.⬆️ The
pathwatcher
npm package has been upgraded to version 7.1.0.⬆️ The
http-proxy
npm package has been upgraded to version 1.16.2.⬆️ The
semver
npm package has been upgraded to version 5.4.1.✅ When running Meteor tool tests (i.e.
./meteor self-test
) during the course of developing Meteor itself, it is no longer necessary to./meteor npm install -g phantomjs-prebuilt browserstack-webdriver
. These will now be installed automatically upon their use.📦 You can now run
meteor test --driver-package user:package
without first runningmeteor add user:package
.⚡️ iOS icons and launch screens have been updated to support iOS 11 Issue #9196 PR #9198
-
v1.6.0.1 Changes
December 08, 2017⬆️ Node has been upgraded to version 8.9.3, an important security release.
⬆️ The
npm
package has been upgraded to version 5.5.1, which supports several new features, including two-factor authentication, as described in the release notes.
-
v1.5.4 Changes
November 08, 2017- 🚀 Node has been updated to version 4.8.6. This release officially includes our fix of a faulty backport of garbage collection-related logic in V8 and ends Meteor's use of a custom Node with that patch. In addition, it includes small OpenSSL updates as announced on the Node blog: https://nodejs.org/en/blog/release/v4.8.6/. Issue #8648
-
v1.5.4.2 Changes
April 02, 2018- ⬆️ Node has been upgraded to version 4.9.0, an important security release.
-
v1.5.4.1 Changes
December 08, 2017- ⬆️ Node has been upgraded to version 4.8.7, an important security release.
-
v1.5.3 Changes
November 04, 2017🔒 Node has been upgraded to version 4.8.5, a recommended security release: https://nodejs.org/en/blog/release/v4.8.5/. While it was expected that Node 4.8.5 would also include our fix of a faulty backport of garbage collection-related logic in V8, the timing of this security release has caused that to be delayed until 4.8.6. Therefore, this Node still includes our patch for this issue. Issue #8648
Various backports from Meteor 1.6, as detailed in the PR for Meteor 1.5.3. Briefly, these involve fixes for:
-
v1.5.2 Changes
September 05, 2017Node 4.8.4 has been patched to include https://github.com/nodejs/node/pull/14829, an important PR implemented by our own @abernix (:tada:), which fixes a faulty backport of garbage collection-related logic in V8 that was causing occasional segmentation faults during Meteor development and testing, ever since Node 4.6.2 (Meteor 1.4.2.3). When Node 4.8.5 is officially released with these changes, we will immediately publish a small follow-up release. Issue #8648
🏗 When Meteor writes to watched files during the build process, it no longer relies on file watchers to detect the change and invalidate the optimistic file system cache, which should fix a number of problems related by the symptom of endless rebuilding. Issue #8988 Issue #8942 PR #9007
⚡️ The
cordova-lib
npm package has been updated to 7.0.1, along with cordova-android (6.2.3) and cordova-ios (4.4.0), and various plugins. PR #8919 resolves the umbrella issue #8686, as well as several Android build issues: #8408, #8424, and #8464.🚀 The
boilerplate-generator
package responsible for generating initial HTML documents for Meteor apps has been refactored by @stevenhao to avoid using thespacebars
-related packages, which means it is now possible to remove Blaze as a dependency from the server as well as the client. PR #8820⬆️ The
meteor-babel
package has been upgraded to version 0.23.1.⬆️ The
reify
npm package has been upgraded to version 0.12.0, which includes a minor breaking change that correctly skips exports nameddefault
inexport * from "module"
declarations. If you have any wrapper modules that re-export another module's exports usingexport * from "./wrapped/module"
, and the wrapped module has adefault
export that you want to be included, you should now explicitly re-exportdefault
using a second declaration:export * from "./wrapped/module"; export { default } "./wrapped/module";
⬆️ The
meteor-promise
package has been upgraded to version 0.8.5, and thepromise
polyfill package has been upgraded to 8.0.1.⬆️ The
semver
npm package has been upgraded to version 5.3.0. PR #8859⬆️ The
faye-websocket
npm package has been upgraded to version 0.11.1, and its dependencywebsocket-driver
has been upgraded to a version containing this fix, thanks to @sdarnell. meteor-feature-requests#160⬆️ The
uglify-js
npm package has been upgraded to version 3.0.28.Thanks to PRs #8960 and #9018 by @GeoffreyBooth, a
coffeescript-compiler
package has been extracted from thecoffeescript
package, similar to how thebabel-compiler
package is separate from theecmascript
package, so that other packages (such asvue-coffee
) can make use ofcoffeescript-compiler
. Allcoffeescript
-related packages have been moved topackages/non-core
, so that they can be published independently from Meteor releases.📦
meteor list --tree
can now be used to list all transitive package dependencies (and versions) in an application. Weakly referenced dependencies can also be listed by using the--weak
option. For more information, runmeteor help list
. PR #8936🏗 The
star.json
manifest created within the root of ameteor build
bundle will now containnodeVersion
andnpmVersion
which will specify the exact versions of Node.js and npm (respectively) which the Meteor release was bundled with. The.node_version.txt
file will still be written into the root of the bundle, but it may be deprecated in a future version of Meteor. PR #8956📦 A new package called
mongo-dev-server
has been created and wired intomongo
as a dependency. As long as this package is included in a Meteor application (which it is by default since all new Meteor apps havemongo
as a dependency), a local development MongoDB server is started alongside the application. This package was created to provide a way to disable the local development Mongo server, whenmongo
isn't needed (e.g. when using Meteor as a build system only). If an application has no dependency onmongo
, themongo-dev-server
package is not added, which means no local development Mongo server is started. Feature Request #31 PR #8853Accounts.config
no longer mistakenly allows tokens to expire when theloginExpirationInDays
option is set tonull
. Issue #5121 PR #8917👍 The
"env"
field is now supported in.babelrc
files. PR #8963Files contained by
client/compatibility/
directories or added withapi.addFiles(files, ..., { bare: true })
are now evaluated before importing modules withrequire
, which may be a breaking change if you depend on the interleaving ofbare
files with eager module evaluation. PR #8972📦 When
meteor test-packages
runs in a browser, uncaught exceptions will now be displayed above the test results, along with the usual summary of test failures, in case those uncaught errors have something to do with later test failures. Issue #4979 PR #9034
-
v1.5.2.2 Changes
October 02, 2017🛠 Fixes a regression in 1.5.2.1 which resulted in the macOS firewall repeatedly asking to "accept incoming network connections". While the
node
binary in 1.5.2.1 was functionally the same as 1.5.2, it had been recompiled on our build farm (which re-compiles all architectures at the same time) to ensure compatibility with older (but still supported) Linux distributions. Unfortunately, macOS took issue with the binary having a different 'signature' (but same 'identifier') as one it had already seen, and refused to permanently "allow" it in the firewall. Our macOSnode
binaries are now signed with a certificate, hopefully preventing this from occurring again. Issue #9139🛠 Fixes a regression in
accounts-base
caused by changes to the (now deprecated)connection.onReconnect
function which caused users to be logged out shortly after logging in. Issue #9140 PR #⚡️
cordova-ios
has been updated to version 4.5.1, to add in iOS 11 / Xcode 9 compatibility. Issue #9098 Issue #9126 PR #9137Includes a follow-up change to the (not commonly necessary)
Npm.require
which ensures built-in modules are loaded first, which was necessary after a change in 1.5.2.1 which reduced its scope. This resolves "Cannot find module crypto" and similar errors. Issue #9136🏁 A bug that prevented building some binary npm packages on Windows has been fixed. Issue #9153