All Versions
239
Latest Version
2.4
Avg Release Cycle
26 days
Latest Release
34 days ago

Changelog History
Page 6

  • v1.9.1 Changes

    February 18, 2020

    💥 Breaking changes

    N/A

    Migration Steps

    N/A

    🔄 Changes

    • ⚡️ Node.js has been updated to version 12.16.0 from 12.14.0, which includes security updates and small changes:

      • 12.16.0
      • Updated V8 to release v7.8 which includes improvements in performance, for example, object destructuring now is as fast as the equivalent variable assignment.
      • 12.15.0
    • cursor.observeChanges now accepts a second options argument. If your observer functions do not mutate the passed arguments, you can specify { nonMutatingCallbacks: true }, which improves performance by reducing the amount of data copies.

  • v1.9.1-rc.1

    February 18, 2020
  • v1.9.1-rc.0

    February 18, 2020
  • v1.9 Changes

    January 09, 2020

    💥 Breaking changes

    • 🐧 Because Node.js 12 no longer supports 32-bit Linux, Meteor 1.9 has also dropped support for 32-bit Linux. In other words, Meteor 1.9 supports 64-bit Mac, Windows, and Linux, as well as 32-bit Windows.

    Migration Steps

    N/A

    🔄 Changes

    • ⚡️ Node.js has been updated to version 12.14.0, which includes several major Node.js versions since 8.17.0 (used by Meteor 1.8.3):

    • ⚡️ The fibers npm package has been updated to version 4.0.3, which includes changes that may drastically reduce garbage collection pressure resulting from heavy Fiber usage.

    • ⚡️ The pathwatcher npm package has been updated to use a fork of version 8.0.2, with PR #128 applied.

    • ⚡️ The sqlite3 npm package has been updated to version 4.1.0.

    • ⚡️ The node-gyp npm package has been updated to version 6.0.1, and node-pre-gyp has been updated to version 0.14.0.

    • The feature that restarts the application up to two times if it crashes on startup has been removed. Feature #335 PR #10345

    • ⚡️ Facebook OAuth has been updated to call v5 API endpoints. PR #10738

    🔄 Changes

    • Meteor.user(), Meteor.findUserByEmail() and Meteor.findUserByUserName() can take a new options parameter which can be used to limit the returned fields. Useful for minimizing DB bandwidth on the server and avoiding unnecessary reactive UI updates on the client. Issue #10469

    • 0️⃣ Accounts.config() has a new option defaultFieldSelector which will apply to all Meteor.user() and Meteor.findUserBy...() functions without explicit field selectors, and also to all onLogin, onLogout and onLoginFailure callbacks. This is useful if you store large data on the user document (e.g. a growing list of transactions) which do no need to be retrieved from the DB whenever you or a package author call Meteor.user() without limiting the fields. Issue #10469

    • Lots of internal calls to Meteor.user() without field specifiers in accounts-base and accounts-password packages have been optimized with explicit field selectors to only fetch the fields needed by the functions they are in. Issue #10469

  • v1.9-rc.3

    January 08, 2020
  • v1.9-rc.2

    January 02, 2020
  • v1.9-rc.1

    December 30, 2019
  • v1.9-rc.0

    December 19, 2019
  • v1.9-beta.4

    November 26, 2019
  • v1.9-beta.3

    November 14, 2019