All Versions
246
Latest Version
2.5
Avg Release Cycle
57 days
Latest Release
1148 days ago

Changelog History
Page 14

  • v1.4.3 Changes

    February 13, 2017
    • 🔖 Versions of Meteor core packages are once again constrained by the current Meteor release.

    🚀 > Before Meteor 1.4, the current release dictated the exact version of every installed core package, which meant newer core packages could not be installed without publishing a new Meteor release. In order to support incremental development of core packages, Meteor 1.4 removed all release-based constraints on core package versions (#7084). Now, in Meteor 1.4.3, core package versions must remain patch-compatible with the versions they had when the Meteor release was published. This middle ground restores meaning to Meteor releases, yet still permits patch updates to core packages.

    • ⚡️ The cordova-lib npm package has been updated to 6.4.0, along with cordova-android (6.1.1) and cordova-ios (4.3.0), and various plugins. #8239

    • 📦 The coffeescript Meteor package has been moved from packages/coffeescript to packages/non-core/coffeescript, so that it will not be subject to the constraints described above.

    • CoffeeScript source maps should be now be working properly in development. #8298

    • 📦 The individual account "service" packages (facebook, google, twitter, github, meteor-developer, meetup and weibo) have been split into:

      • <service>-oauth (which interfaces with the <service> directly) and
      • <service>-config-ui (the Blaze configuration templates for accounts-ui)

    This means you can now use accounts-<service> without needing Blaze.

    If you are using accounts-ui and accounts-<service>, you will probably need to install the <service>-config-ui package if you want to configure it using the Accounts UI.

    • Issue #7715
    • PR(facebook) #7728
    • PR(google) #8275
    • PR(twitter) #8283
    • PR(github) #8303
    • PR(meteor-developer) #8305
    • PR(meetup) #8321

    • PR(weibo) #8302

      • 📦 The url and http packages now encode to a less error-prone format which more closely resembles that used by PHP, Ruby, jQuery.param and others. Objects and Arrays can now be encoded, however, if you have previously relied on Arrays passed as params being simply join-ed with commas, you may need to adjust your HTTP.call implementations. #8261 and #8342.
      • 📦 The npm npm package is still at version 4.1.2 (as it was when Meteor 1.4.3 was originally published), even though npm was downgraded to 3.10.9 in Meteor 1.4.2.7.
      • ⬆️ The meteor-babel npm package has been upgraded to version 0.14.3, fixing #8021 and #7662.
      • ⬆️ The reify npm package has been upgraded to 0.4.7.
      • ➕ Added support for frame-ancestors CSP option in browser-policy. #7970
      • 📦 You can now use autoprefixer with stylus files added via packages. #7727
      • ⏪ Restored #8213 after those changes were reverted in v1.4.2.5.
      • 📦 npm dependencies of Meteor packages will now be automatically rebuilt if the npm package's package.json file has "scripts" section containing a preinstall, install, or postinstall command, as well as when the npm package contains any .node files. Discussion here.
      • The meteor create command now runs meteor npm install automatically to install dependencies specified in the default package.json file. #8108

  • v1.4.3.2 Changes

    March 14, 2017

    • ⬆️ Node has been upgraded to version 4.8.0.

    • ⬆️ The npm npm package has been upgraded to version 4.3.0.

    • ⬆️ The node-gyp npm package has been upgraded to 3.5.0.

    • ⚡️ The node-pre-gyp npm package has been updated to 0.6.33.

    • The bundled version of MongoDB used by meteor run in development has been upgraded to 3.2.12.

    • 📦 The mongodb npm package used by the npm-mongo Meteor package has been updated to version 2.2.24. PR #8453 Issue #8449

    • 📦 The check package has had its copy of jQuery.isPlainObject updated to a newer implementation to resolve an issue where the nodeType property of an object couldn't be checked, fixing #7354.

    • 📦 The standard-minifier-js and minifier-js packages now have improved error capturing to provide more information on otherwise unhelpful errors thrown when UglifyJS encounters ECMAScript grammar it is not familiar with. #8414

    • Similar in behavior to Meteor.loggingIn(), accounts-base now offers a reactive Meteor.loggingOut() method (and related Blaze helpers, loggingOut and loggingInOrOut). PR #8271 Issue #1331 Issue #769

    • Using length as a selector field name and with a Number as a value in a Mongo.Collection transformation will no longer cause odd results. #8329.

    • 👍 observe-sequence (and thus Blaze) now properly supports Arrays which were created in a vm or across frame boundaries, even if they were sub-classed. Issue #8160 PR #8401

    • 👍 Minimongo now supports $bitsAllClear, $bitsAllSet, $bitsAnySet and $bitsAnyClear. #8350

    • A new [Development.md](DEVELOPMENT.md) document has been created to provide an easier path for developers looking to make contributions to Meteor Core (that is, the meteor tool itself) along with plenty of helpful reminders for those that have already done so! #8267

    • 📦 The suggestion to add a {oauth-service}-config-ui package will no longer be made on the console if service-configuration package is already installed. Issue #8366 PR #8429

    • Meteor.apply's throwStubExceptions option is now properly documented in the documentation whereas it was previously only mentioned in the Guide. Issue #8435 PR #8443

    • DDPRateLimiter.addRule now accepts a callback which will be executed after a rule is executed, allowing additional actions to be taken if necessary. Issue #5541 PR #8237

    • 📦 jquery is no longer a dependency of the http package. #8389

    • 📦 jquery is no longer in the default package list after running meteor create, however is still available thanks to blaze-html-templates. If you still require jQuery, the recommended approach is to install it from npm with meteor npm install --save jquery and then import-ing it into your application. #8388

    • ⚡️ The shell-server package (i.e. meteor shell) has been updated to more gracefully handle recoverable errors (such as SyntaxErrors) in the same fashion as the Node REPL. Issue #8290 PR #8446

    • 📦 The webapp package now reveals a WebApp.connectApp to make it easier to provide custom error middleware. #8403

    • ⚡️ The meteor update --all-packages command has been properly documented in command-line help (i.e. meteor update --help). PR #8431 Issue #8154

    • 📦 Syntax errors encountered while scanning package.json files for binary dependencies are now safely and silently ignored. Issue #8427 PR #8468

  • v1.4.3.1 Changes

    February 14, 2017

    • ⬆️ The meteor-babel npm package has been upgraded to version 0.14.4, fixing #8349.

    • ⬆️ The reify npm package has been upgraded to version 0.4.9.

    • Partial npm-shrinkwrap.json files are now disregarded when (re)installing npm dependencies of Meteor packages, fixing #8349. Further discussion of the new npm behavior can be found here.

  • v1.4.2 Changes

    October 25, 2016
    • 🚀 This release implements a number of rebuild performance optimizations. As you edit files in development, the server should restart and rebuild much more quickly, especially if you have many node_modules files. See https://github.com/meteor/meteor/pull/7668 for more details.

    Note: the METEOR_PROFILE environment variable now provides data for server startup time as well as build time, which should make it easier to tell which of your packages are responsible for slow startup times. Please include the output of METEOR_PROFILE=10 meteor run with any GitHub issue about rebuild performance.

    • ⬆️ npm has been upgraded to version 3.10.9.

    • ⚡️ The cordova-lib npm package has been updated to 6.3.1, along with cordova-android (5.2.2) and cordova-ios (4.2.1), and various plugins.

    • ⚡️ The node-pre-gyp npm package has been updated to 0.6.30.

    • ⚡️ The lru-cache npm package has been updated to 4.0.1.

    • ⚡️ The meteor-promise npm package has been updated to 0.8.0 for better asynchronous stack traces.

    • The meteor tool is now prevented from running as root as this is not recommended and can cause issues with permissions. In some environments, (e.g. Docker), it may still be desired to run as root and this can be permitted by passing --unsafe-perm to the meteor command. #7821

    • 📦 Blaze-related packages have been extracted to meteor/blaze, and the main meteor/meteor repository now refers to them via git submodules (see #7633). When running meteor from a checkout, you must now update these submodules by running

      git submodule update --init --recursive

      in the root directory of your meteor checkout.

    • 🔀 Accounts.forgotPassword and .verifyEmail no longer throw errors if callback is provided. Issue #5664 Origin PR #5681 Merged PR

    • 🔒 The default content security policy (CSP) for Cordova now includes ws: and wss: WebSocket protocols. #7774

    • 🔧 meteor npm commands are now configured to use dev_bundle/.npm as the npm cache directory by default, which should make npm commands less sensitive to non-reproducible factors in the external environment. https://github.com/meteor/meteor/pull/7668/commits/3313180a6ff33ee63602f7592a9506012029e919

    • 🚀 The meteor test command now supports the --no-release-check flag. https://github.com/meteor/meteor/pull/7668/commits/7097f78926f331fb9e70a06300ce1711adae2850

    • JavaScript module bundles on the server no longer include transitive node_modules dependencies, since those dependencies can be evaluated directly by Node. This optimization should improve server rebuild times for apps and packages with large node_modules directories. https://github.com/meteor/meteor/pull/7668/commits/03c5346873849151cecc3e00606c6e5aa13b3bbc

    • 📦 The standard-minifier-css package now does basic caching for the expensive mergeCss function. https://github.com/meteor/meteor/pull/7668/commits/bfa67337dda1e90610830611fd99dcb1bd44846a

    • 📦 The coffeescript package now natively supports import and export declarations. #7818

    • Due to changes in how Cordova generates version numbers for iOS and Android apps, you may experience issues with apps updating on user devices. To avoid this, consider managing the buildNumber manually using App.info('buildNumber', 'XXX'); in mobile-config.js. There are additional considerations if you have been setting android:versionCode or ios-CFBundleVersion. See #7205 and #6978 for more information.

  • v1.4.2.7 Changes

    February 13, 2017
    • ⬇️ The npm npm package has been downgraded from version 4.1.2 back to version 3.10.9, reverting the upgrade in Meteor 1.4.2.4.

  • v1.4.2.6 Changes

    February 08, 2017
    • 🛠 Fixed a critical bug that was introduced by the fix for Issue #8136, which caused some npm packages in nested node_modules directories to be omitted from bundles produced by meteor build and meteor deploy.

  • v1.4.2.5 Changes

    February 03, 2017
    • ⏪ Reverted #8213 as the change was deemed too significant for this release.

    ⏪ > Note: The decision to revert the above change was made late in the Meteor 1.4.2.4 release process, before it was ever recommended but too late in the process to avoid the additional increment of the version number. See #8311 for additional information. This change will still be released in an upcoming version of Meteor with a more seamless upgrade.

  • v1.4.2.4 Changes

    February 02, 2017

    • ⬆️ Node has been upgraded to version 4.7.3.

    • ⬆️ The npm npm package has been upgraded from version 3.10.9 to 4.1.2.

    🚀 > Note: This change was later deemed too substantial for a point release and was reverted in Meteor 1.4.2.7.

    • 🛠 Fix for Issue #8136.

    • 🛠 Fix for Issue #8222.

    • 🛠 Fix for Issue #7849.

    • 🏁 The version of 7-zip included in the Windows dev bundle has been upgraded from 1602 to 1604 in an attempt to mitigate Issue #7688.

    • 📦 The "main" field of package.json modules will no longer be overwritten with the value of the optional "browser" field, now that the install npm package can make sense of the "browser" field at runtime. If you experience module resolution failures on the client after updating Meteor, make sure you've updated the modules-runtime Meteor package to at least version 0.7.8. #8213

  • v1.4.2.3 Changes

    November 17, 2016
    • 💅 Style improvements for meteor create --full. #8045

    Note: Meteor 1.4.2.2 was finalized before #8045 was merged, but those changes were deemed important enough to skip recommending 1.4.2.2 and instead immediately release 1.4.2.3.

  • v1.4.2.2 Changes

    November 15, 2016

    • ⬆️ Node has been upgraded to version 4.6.2.

    • meteor create now has a new --full option, which generates an larger app, demonstrating development techniques highlighted in the Meteor Guide

    Issue #6974 PR #7807

    • 👍 Minimongo now supports $min, $max and partially supports $currentDate.

    Issue #7857 PR #7858

    • 🛠 Fix for Issue #5676 PR #7968

    • It is now possible for packages to specify a lazy main module:

      Package.onUse(function (api) {
api.mainModule("client.js", "client", { lazy: true });
});

      This means the client.js module will not be evaluated during app startup unless/until another module imports it, and will not even be included in the client bundle if no importing code is found. Note 1: packages with lazy main modules cannot use api.export to export global symbols to other packages/apps. Note 2: packages with lazy main modules should be restricted to Meteor 1.4.2.2 or later via api.versionsFrom("1.4.2.2"), since older versions of Meteor cannot import lazy main modules using import "meteor/<package name>" but must explicitly name the module: import "meteor/<package name>/client.js".