Changelog History
Page 15
-
v1.4.2.1 Changes
November 08, 2016📦 Installing the
babel-runtime
npm package in your applicationnode_modules
directory is now required for most Babel-transformed code to work, as the Meteorbabel-runtime
package no longer attempts to provide custom implementations of Babel helper functions. To install thebabel-runtime
package, simply run the commandmeteor npm install --save babel-runtime
in any Meteor application directory. The Meteor
babel-runtime
package version has been bumped to 1.0.0 to reflect this major change. #7995File system operations performed by the command-line tool no longer use fibers unless the
METEOR_DISABLE_FS_FIBERS
environment variable is explicitly set to a falsy value. For larger apps, this change results in significant build performance improvements due to the creation of fewer fibers and the avoidance of unnecessary asyncronous delays. https://github.com/meteor/meteor/pull/7975/commits/ca4baed90ae0675e55c93976411d4ed91f12dd63⚙ Running Meteor as
root
is still discouraged, and results in a fatal error by default, but the--allow-superuser
flag now works as claimed. #7959⏪ The
dev_bundle\python\python.exe
executable has been restored to the Windows dev bundle, which may help withmeteor npm rebuild
commands. #7960🔄 Changes within linked npm packages now trigger a partial rebuild, whereas previously (in 1.4.2) they were ignored. #7978
🛠 Miscellaneous fixed bugs: #2876 #7154 #7956 #7974 #7999 #8005 #8007
-
v1.4.1 Changes
August 18, 2016⬆️ Node has been upgraded to 4.5.0.
⬆️
npm
has been upgraded to 3.10.6.The
meteor publish-for-arch
command is no longer necessary when publishing Meteor packages with binary npm dependencies. Instead, binary dependencies will be rebuilt automatically on the installation side. Meteor package authors are not responsible for failures due to compiler toolchain misconfiguration, and any compilation problems with the underlying npm packages should be taken up with the authors of those packages. That said, if a Meteor package author really needs or wants to continue usingmeteor publish-for-arch
, she should publish her package using an older release: e.g.meteor --release 1.4 publish
. #7608The
.meteor-last-rebuild-version.json
files that determine if a binary npm package needs to be rebuilt now include more information from theprocess
object, namelyprocess.{platform,arch,versions}
instead of justprocess.versions
. Note also that the comparison of versions now ignores differences in patch versions, to avoid needless rebuilds.📦 The
npm-bcrypt
package now uses a pure-JavaScript implementation by default, but will prefer the nativebcrypt
implementation if it is installed in the application'snode_modules
directory. In other words, runmeteor install --save bcrypt
in your application if you need or want to use the native implementation ofbcrypt
. #7595📦 After Meteor packages are downloaded from Atmosphere, they will now be extracted using native
tar
or7z.exe
on Windows, instead of the https://www.npmjs.com/package/tar library, for a significant performance improvement. #7457⬆️ The npm
tar
package has been upgraded to 2.2.1, though it is now only used as a fallback after nativetar
and/or7z.exe
.The progress indicator now distinguishes between downloading, extracting, and loading newly-installed Meteor packages, instead of lumping all of that work into a "downloading" status message.
⚡️ Background Meteor updates will no longer modify the
~/.meteor/meteor
symbolic link (orAppData\Local\.meteor\meteor.bat
on Windows). Instead, developers must explicitly typemeteor update
to begin using a new version of themeteor
script.0️⃣ Password Reset tokens now expire (after 3 days by default -- can be modified via
Accounts.config({ passwordResetTokenExpirationInDays: ...}
). PR #7534📦 The
google
package now uses theemail
scope as a mandatory field instead of theprofile
scope. Theprofile
scope is still added by default if therequestPermissions
option is not specified to maintain backward compatibility, but it is now possible to pass an empty array torequestPermissions
in order to only request theemail
scope, which reduces the amount of permissions requested from the user in the Google popup. PR #6975➕ Added
Facebook.handleAuthFromAccessToken
in the case where you get the FB accessToken in some out-of-band way. PR #7550Accounts.onLogout
gets{ user, connection }
context in a similar fashion toAccounts.onLogin
. Issue #7397 PR #7433The
node-gyp
andnode-pre-gyp
tools will now be installed inbundle/programs/server/node_modules
, to assist with rebuilding binary npm packages when deploying an app to Galaxy or elsewhere. #7571📦 The
standard-minifier-{js,css}
packages no longer minify .js or .css files on the server. #7572Multi-line input to
meteor shell
, which was broken by changes to therepl
module in Node 4, works again. #7562The implementation of the command-line
meteor
tool now forbids misbehaving polyfill libraries from overwritingglobal.Promise
. #7569📦 The
oauth-encryption
package no longer depends on thenpm-node-aes-gcm
package (or any special npm packages), because the Node 4crypto
library natively supports theaes-128-gcm
algorithm. #7548🚚 The server-side component of the
meteor shell
command has been moved into a Meteor package, so that it can be developed independently from the Meteor release process, thanks to version unpinning. #7624✅ The
meteor shell
command now works when runningmeteor test
.The
meteor debug
command no longer pauses at the first statement in the Node process, yet still reliably stops at custom breakpoints it encounters later.⬆️ The
meteor-babel
package has been upgraded to 0.12.0.⬆️ The
meteor-ecmascript-runtime
package has been upgraded to 0.2.9, to support several additional stage 4 proposals.📦 A bug that prevented @-scoped npm packages from getting bundled for deployed apps has been fixed. #7609.
⚡️ The
meteor update
command now supports an--all-packages
flag to update all packages (including indirect dependencies) to their latest compatible versions, similar to passing the names of all your packages to themeteor update
command. #7653🚀 Background release updates can now be disabled by invoking either
meteor --no-release-check
orMETEOR_NO_RELEASE_CHECK=1 meteor
. #7445
-
v1.4.1.3 Changes
October 21, 2016⚡️ Node has been updated to version 4.6.1: https://nodejs.org/en/blog/release/v4.6.1/
📦 The
mongodb
npm package used by thenpm-mongo
Meteor package has been updated to version 2.2.11. #7780⬆️ The
fibers
npm package has been upgraded to version 1.0.15.⚙ Running Meteor with a different
--port
will now automatically reconfigure the Mongo replica set when using the WiredTiger storage engine, instead of failing to start Mongo. #7840.When the Meteor development server shuts down, it now attempts to kill the
mongod
process it spawned, in addition to killing any runningmongod
processes when the server first starts up. https://github.com/meteor/meteor/pull/7668/commits/295d3d5678228f06ee0ab6c0d60139849a0ea192The
meteor <command> ...
syntax will now work for any command installed indev_bundle/bin
, except for Meteor's own commands.📦 Incomplete package downloads will now fail (and be retried several times) instead of silently succeeding, which was the cause of the dreaded
Error: ENOENT: no such file or directory, open... os.json
error. #7806
-
v1.4.1.2 Changes
October 04, 2016🚀 Node has been upgraded to version 4.6.0, a recommended security release: https://nodejs.org/en/blog/release/v4.6.0/
⬆️
npm
has been upgraded to version 3.10.8.
-
v1.4.1.1 Changes
August 24, 2016- ⚡️ Update the version of our Node MongoDB driver to 2.2.8 to fix a bug in
reconnection logic, leading to some
update
andremove
commands being treated asinsert
s. #7594
- ⚡️ Update the version of our Node MongoDB driver to 2.2.8 to fix a bug in
reconnection logic, leading to some
-
v1.4 Changes
July 25, 2016⬆️ Node has been upgraded to 4.4.7.
⬆️ The
meteor-babel
npm package has been upgraded to 0.11.7.⬆️ The
reify
npm package has been upgraded to 0.3.6.⬆️ The
bcrypt
npm package has been upgraded to 0.8.7.📦 Nested
import
declarations are now enabled for package code as well as application code. 699cf1f38e9b2a074169515d23983f74148c7223⬆️ Meteor has been upgraded to support Mongo 3.2 by default (the bundled version used by
meteor run
has been upgraded). Internally it now uses the 2.2.4 version of themongodb
npm driver, and has been tested against at Mongo 3.2 server. Issue #6957
Mongo 3.2 defaults to the new WiredTiger storage engine. You can update your database following the instructions here: https://docs.mongodb.com/v3.0/release-notes/3.0-upgrade/. In development, you can also just use
meteor reset
to remove your old database, and Meteor will create a new WiredTiger database for you. The Mongo driver will continue to work with the old MMAPv1 storage engine however.The new version of the Mongo driver has been tested with MongoDB versions from 2.6 up. Mongo 2.4 has now reached end-of-life (https://www.mongodb.com/support-policy), and is no longer supported.
If you are setting
MONGO_OPLOG_URL
, especially in production, ensure you are passing in thereplicaSet
argument (see #7450)Custom Mongo options can now be specified using the
Mongo.setConnectionOptions(options)
API. #7277On the server, cursor.count() now takes a single argument
applySkipLimit
(see the corresponding Mongo documentation)🛠 Fix for regression caused by #5837 which incorrectly rewrote network-path references (e.g.
//domain.com/image.gif
) in CSS URLs. #7416➕ Added Angular2 boilerplate example #7364
-
v1.4.0.1 Changes
July 29, 2016🛠 Fix issue with the 1.4 tool springboarding to older releases (see Issue #7491)
🛠 Fix issue with running in development on Linux 32bit Issue #7511
-
v1.3.5 Changes
July 16, 2016📦 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 innode_modules
will be built into the production bundle. In other words, make sure you have apackage.json
file if you want to benefit fromdevDependencies
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 tometeor {node,npm}
, thenode-gyp
tool will infer the appropriate version (though it still defaults to "2015").
-
v1.3.5.1 Changes
July 18, 2016- 🚀 This release fixed a small bug in 1.3.5 that prevented updating apps
whose
.meteor/release
files refer to releases no longer installed in~/.meteor/packages/meteor-tool
. 576468eae8d8dd7c1fe2fa381ac51dee5cb792cd
- 🚀 This release fixed a small bug in 1.3.5 that prevented updating apps
whose
-
v1.3.4 Changes
June 22, 2016The version of
npm
used bymeteor npm
and when installingNpm.depends
dependencies of Meteor packages has been upgraded from 2.15.1 to 3.9.6, which should lead to much flatter node_modules dependency trees.⬆️ The
meteor-babel
npm package has been upgraded to 0.11.6, and is now installed using[email protected]
, fixing bugs arising from Windows path limits, such as #7247.⬆️ The
reify
npm package has been upgraded to 0.3.4, fixing #7250.Thanks to caching improvements for the
files.{stat,lstat,readdir,realpath}
methods andPackageSource#_findSources
, development server restart times are no longer proportional to the number of files innode_modules
directories. #7253 #7008🏁 When installed via
InstallMeteor.exe
on Windows, Meteor can now be easily uninstalled through the "Programs and Features" control panel.⏱ HTTP requests made by the
meteor
command-line tool now have a timeout of 30 seconds, which can be adjusted by the$TIMEOUT_SCALE_FACTOR
environment variable. #7143⬆️ The
request
npm dependency of thehttp
package has been upgraded from 2.53.0 to 2.72.0.✅ The
--headless
option is now supported bymeteor test
andmeteor test-packages
, in addition tometeor self-test
. #7245