meteor v1.4 Release Notes

Release Date: 2016-07-25 // over 7 years ago
    • ⬆️ 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 the mongodb 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 the replicaSet argument (see #7450)

    • Custom Mongo options can now be specified using the Mongo.setConnectionOptions(options) API. #7277

    • On 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