All Versions
Latest Version
Avg Release Cycle
57 days
Latest Release
469 days ago

Changelog History
Page 10

  • v1.8.2-beta.17

    July 30, 2019
  • v1.8.2-beta.16

    July 15, 2019
  • v1.8.2-beta.15

    July 06, 2019
  • v1.8.2-beta.14

    July 05, 2019
  • v1.8.2-beta.13

    July 04, 2019
  • v1.8.2-beta.12

    July 03, 2019
  • v1.8.2-beta.11

    July 02, 2019
  • v1.8.1 Changes

    April 03, 2019

    ๐Ÿ’ฅ Breaking changes

    • Although we are not aware of any specific backwards incompatibilities, the major upgrade of cordova-android from 6.4.0 to 7.1.4 likely deserves extra attention, if you use Cordova to build Android apps.

    Migration Steps


    ๐Ÿ”„ Changes

    Note: While Node 8.12.0 included changes that may improve the performance of Meteor apps, there have been reports of CPU usage spikes in production due to excessive garbage collection, so this version of Meteor should be considered experimental until those problems have been fixed. Issue #10216

    • โฌ†๏ธ The npm tool has been upgraded to version 6.9.0, and our fork of its pacote dependency has been updated to version 9.5.0.

    • โฌ†๏ธ Mongo has been upgraded to version 4.0.6 for 64-bit systems (was 4.0.2), and 3.2.22 for 32-bit systems (was 3.2.19). The mongodb npm package used by npm-mongo has been updated to version 3.1.13 (was 3.1.6).

    • โšก๏ธ The fibers npm package has been updated to version 3.1.1, a major update from version 2.0.0. Building this version of fibers requires a C++11 compiler, unlike previous versions. If you deploy your Meteor app manually (without using Galaxy), you may need to update the version of g++ used when running npm install in the bundle/programs/server directory.

    • โšก๏ธ The meteor-babel npm package has been updated to version 7.3.4.

    • Cordova Hot Code Push mechanism is now switching versions explicitly with call to WebAppLocalServer.switchToPendingVersion instead of trying to switch every time a browser reload is detected. If you use any third party package or have your own HCP routines implemented be sure to call it before forcing a browser reload. If you use the automatic reload from the Reload meteor package you do not need to do anything. cordova-plugin-meteor-webapp PR #62

    • ๐Ÿ— Multiple Cordova-related bugs have been fixed, including Xcode 10 build incompatibilities and hot code push errors due to duplicated images/assets. PR #10339

    • The cordova-android and cordova-ios npm dependencies have been updated to 7.1.4 (from 6.4.0) and 4.5.5 (from 4.5.4), respectively.

    • ๐ŸŽ Build performance has improved (especially on Windows) thanks to additional caching implemented by @zodern in PRs #10399, #10452, #10453, and #10454.

    • The meteor mongo command no longer uses the --quiet option, so the normal startup text will be displayed, albeit without the banner about Mongo's free monitoring service. See this MongoDB Jira issue for more details.

    • ๐Ÿ“ฆ In Meteor packages, client/ and server/ directories no longer have any special meaning. In application code, client/ directories are ignored during the server build, and server/ directories are ignored during the client build, as before. This special behavior previously applied to packages as well, but has now been removed. Issue #10393 PR #10414

    • If your application is using Git for version control, the current Git commit hash will now be exposed via the Meteor.gitCommitHash property while the app is running (in both server and client code), and also via the "gitCommitHash" property in the star.json file located in the root directory of builds produced by meteor build, for consumption by deployment tools. If you are not using Git, neither property will be defined. PR #10442

    • The Meteor Tool now uses a more reliable method (the MongoDB isMaster command) to detect when the local development database has started and is ready to accept read and write operations. PR #10500

    • Setting the x-no-compression request header will prevent the webapp package from compressing responses with gzip, which may be useful if your Meteor app is behind a proxy that compresses resources with another compression algorithm, such as brotli. PR #10378

  • v1.8 Changes

    October 08, 2018

    ๐Ÿ’ฅ Breaking changes


    Migration Steps

    • โšก๏ธ Update the @babel/runtime npm package to version 7.0.0 or later:
      meteor npm install @babel/[email protected]

    ๐Ÿ”„ Changes

    • ๐Ÿš€ Although Node 8.12.0 has been released, Meteor 1.8 still uses Node 8.11.4, due to concerns about excessive garbage collection and CPU usage in production. To enable Galaxy customers to use Node 8.12.0, we are planning a quick follow-up Meteor 1.8.1 release, which can be obtained by running the command

      meteor update --release 1.8.1-beta.n

      where -beta.n is the latest beta release according to the releases page (currently -beta.6). Issue #10216 PR #10248

    • ๐Ÿ’ป Meteor 1.7 introduced a new client bundle called web.browser.legacy in addition to the web.browser (modern) and web.cordova bundles. Naturally, this extra bundle increased client (re)build times. Since developers spend most of their time testing the modern bundle in development, and the legacy bundle mostly provides a safe fallback in production, Meteor 1.8 cleverly postpones building the legacy bundle until just after the development server restarts, so that development can continue as soon as the modern bundle has finished building. Since the legacy build happens during a time when the build process would otherwise be completely idle, the impact of the legacy build on server performance is minimal. Nevertheless, the legacy bundle still gets rebuilt regularly, so any legacy build errors will be surfaced in a timely fashion, and legacy clients can test the new legacy bundle by waiting a bit longer than modern clients. Applications using the autoupdate or hot-code-push packages will reload modern and legacy clients independently, once each new bundle becomes available. Issue #9948 PR #10055

    • ๐Ÿ”Œ Compiler plugins that call inputFile.addJavaScript or inputFile.addStylesheet may now delay expensive compilation work by passing partial options ({ path, hash }) as the first argument, followed by a callback function as the second argument, which will be called by the build system once it knows the module will actually be included in the bundle. For example, here's the old implementation of BabelCompiler#processFilesForTarget:

      processFilesForTarget(inputFiles) {
      inputFiles.forEach(inputFile => {
        var toBeAdded = this.processOneFileForTarget(inputFile);
        if (toBeAdded) {

      and here's the new version:

      processFilesForTarget(inputFiles) {
      inputFiles.forEach(inputFile => {
        if (inputFile.supportsLazyCompilation) {
            path: inputFile.getPathInPackage(),
            hash: inputFile.getSourceHash(),
          }, function () {
            return this.processOneFileForTarget(inputFile);
        } else {
          var toBeAdded = this.processOneFileForTarget(inputFile);
          if (toBeAdded) {

      If you are an author of a compiler plugin, we strongly recommend using this new API, since unnecessary compilation of files that are not included in the bundle can be a major source of performance problems for compiler plugins. Although this new API is only available in Meteor 1.8, you can use inputFile.supportsLazyCompilation to determine dynamically whether the new API is available, so you can support older versions of Meteor without having to publish multiple versions of your package. [PR


    • ๐Ÿ†• New React-based Meteor applications can now be created using the command

      meteor create --react new-react-app

      Though relatively simple, this application template reflects the ideas of many contributors, especially @dmihal and @alexsicart, and it will no doubt continue to evolve in future Meteor releases. Feature #182 PR #10149

    • ๐Ÿ“ฆ The .meteor/packages file supports a new syntax for overriding problematic version constraints from packages you do not control.

    If a package version constraint in .meteor/packages ends with a ! character, any other (non-!) constraints on that package elsewhere in the application will be weakened to allow any version greater than or equal to the constraint, even if the major/minor versions do not match.

    For example, using both CoffeeScript 2 and practicalmeteor:mocha used to be impossible (or at least very difficult) because of this api.versionsFrom("1.3") statement, which unfortunately constrained the coffeescript package to version 1.x. In Meteor 1.8, if you want to update coffeescript to 2.x, you can relax the practicalmeteor:mocha constraint by putting

      [email protected]_1! # note the !

    in your .meteor/packages file. The coffeescript version still needs to be at least 1.x, so that practicalmeteor:mocha can count on that minimum. However, practicalmeteor:mocha will no longer constrain the major version of coffeescript, so [email protected]_1 will work.

    Feature #208 Commit 4a70b12e Commit 9872a3a7

    • โฌ†๏ธ The npm package has been upgraded to version 6.4.1, and our fork of its pacote dependency has been rebased against version 8.1.6.

    • โšก๏ธ The node-gyp npm package has been updated to version 3.7.0, and the node-pre-gyp npm package has been updated to version 0.10.3.

    • Scripts run via meteor npm ... can now use the meteor command more safely, since the PATH environment variable will now be set so that meteor always refers to the same meteor used to run meteor npm. PR #9941

    • Minimongo's behavior for sorting fields containing an array is now compatible with the behavior of Mongo 3.6+. Note that this means it is now incompatible with the behavior of earlier MongoDB versions. PR #10214

    • โšก๏ธ Meteor's self-test has been updated to use "headless" Chrome rather than PhantomJS for browser tests. PhantomJS can still be forced by passing the --phantom flag to the meteor self-test command. PR #9814

    • Importing a directory containing an index.* file now works for non-.js file extensions. As before, the list of possible extensions is defined by which compiler plugins you have enabled. PR #10027

    • Any client (modern or legacy) may now request any static JS or CSS web.browser or web.browser.legacy resource, even if it was built for a different architecture, which greatly simplifies CDN setup if your CDN does not forward the User-Agent header to the origin. Issue #9953 PR #9965

    • Cross-origin dynamic import() requests will now succeed in more cases. PR #9954

    • Dynamic CSS modules (which are compiled to JS and handled like any other JS module) will now be properly minified in production and source mapped in development. PR #9998

    • ๐Ÿ”€ While CSS is only minified in production, CSS files must be merged together into a single stylesheet in both development and production. This merging is cached by standard-minifier-css so that it does not happen on every rebuild in development, but not all CSS minifier packages use the same caching techniques. Thanks to 1ed095c36d, this caching is now performed within the Meteor build tool, so it works the same way for all CSS minifier packages, which may eliminate a few seconds of rebuild time for projects with lots of CSS.

    • โšก๏ธ The meteor-babel npm package used by babel-compiler has been updated to version 7.1.0. Note: This change requires also updating the @babel/runtime npm package to version 7.0.0-beta.56 or later:

      meteor npm install @babel/[email protected]

      meteor-babel issue #22

    • The @babel/preset-env and @babel/preset-react presets will be ignored by Meteor if included in a .babelrc file, since Meteor already provides equivalent/superior functionality without them. However, you should feel free to leave these plugins in your .babelrc file if they are needed by external tools.

    • โšก๏ธ The install npm package used by modules-runtime has been updated to version 0.12.0.

    • โšก๏ธ The reify npm package has been updated to version 0.17.3, which introduces the, {...}) runtime method as a replacement for, {...}). Note: in future versions of reify and Meteor, the runtime API will be removed, but for now it still exists (and is used to implement, so that existing code will continue to work without recompilation.

    • ๐Ÿ“ฆ The uglify-es npm package used by minifier-js has been replaced with [email protected], a fork of uglify-es that appears to be (more actively) maintained. Issue #10042

    • โšก๏ธ Mongo has been updated to version 4.0.2 and the mongodb npm package used by npm-mongo has been updated to version 3.1.6. PR #10058 Feature Request #269

    • ๐Ÿ”Œ When a Meteor application uses a compiler plugin to process files with a particular file extension (other than .js or .json), those file extensions should be automatically appended to imports that do not resolve as written. However, this behavior was not previously enabled for modules inside node_modules. Thanks to 8b04c25390, the same file extensions that are applied to modules outside the node_modules directory will now be applied to those within it, though .js and .json will always be tried first.

    • As foreshadowed in this talk about Meteor 1.7's modern/legacy bundling system (slides), Meteor now provides an isomorphic implementation of the WHATWG fetch() API, which can be installed by running

      meteor add fetch

      This package is a great demonstration of the modern/legacy bundling system, since it has very different implementations in modern browsers, legacy browsers, and Node. PR #10029

    • The bundle-visualizer package has received a number of UI improvements thanks to work by @jamesmillerburgess in PR #10025. Feature #310

    • Sub-resource integrity hashes (sha512) can now be enabled for static CSS and JS assets by calling WebAppInternals.enableSubresourceIntegrity(). PR #9933 PR #10050

    • The environment variable METEOR_PROFILE=milliseconds now works for the build portion of the meteor build and meteor deploy commands. Feature #239

    • ๐Ÿ”Œ Babel compiler plugins will now receive a caller option of the following form:

      { name: "meteor", arch }

      where arch is the target architecture, e.g. os.*, web.browser, web.cordova, or web.browser.legacy. PR #10211

  • v1.8.0.2 Changes

    January 07, 2019

    ๐Ÿ’ฅ Breaking changes


    Migration steps


    ๐Ÿ”„ Changes

    • The React tutorial has been updated to address a number of inaccuracies due to changes in recent Meteor releases that were not fully incorporated back into the tutorial. As a reminder, Meteor now supports a meteor create --react command that can be used to create a new React-based app quickly.

    • โœ… Fixed a bug where modules named with *.app-tests.js (or *.tests.js) file extensions sometimes could not be imported by the meteor.testModule entry point when running the meteor test command (or meteor test --full-app). PR #10402

    • โšก๏ธ The meteor-promise package has been updated to version 0.8.7, which includes a commit that should prevent memory leaks when excess fibers are discarded from the Fiber pool.

    • โšก๏ธ The meteor-babel npm package has been updated to version 7.2.0, improving source maps for applications with custom .babelrc files.