Migrating to Meteor 2.4

Most of the new features in Meteor 2.4 are either applied directly behind the scenes (in a backwards compatible manner) or are opt-in. For a complete breakdown of the changes, please refer to the changelog.

The above being said, there are a few items that you should implement to have easier time in the future.

createIndex

Previously undocumented _ensureIndex has been aligned with MongoDB breaking change in naming and is now usable as createIndex. Use of _ensureIndex is now deprecated and will throw a warning in development for you.

Email 2.2

The email package had a feature update. You can now override the sending functionality completely with Email.customTransport or if you are using known services you can now ditch the MAIL_URL environment variable and set it in your settings.json file, like so:

{
  "packages": {
    "email": {
      "service": "Mailgun",
      "user": "postmaster@meteor.com",
      "password": "superDuperPassword"
    }
  }
}

Migrating from a version older than 2.3?

If you’re migrating from a version of Meteor older than Meteor 2.3, there may be important considerations not listed in this guide (which specifically covers 2.2 to 2.3). Please review the older migration guides for details:

• Migrating to Meteor 2.3 (from 2.2)
• Migrating to Meteor 2.2 (from 2.0)
• Migrating to Meteor 2.0 (from 1.12)
• Migrating to Meteor 1.12 (from 1.11)
• Migrating to Meteor 1.11 (from 1.10.2)
• Migrating to Meteor 1.10.2 (from 1.10)
• Migrating to Meteor 1.10 (from 1.9.3)
• Migrating to Meteor 1.9.3 (from 1.9)
• Migrating to Meteor 1.9 (from 1.8.3)
• Migrating to Meteor 1.8.3 (from 1.8.2)
• Migrating to Meteor 1.8.2 (from 1.8)
• Migrating to Meteor 1.8 (from 1.7)
• Migrating to Meteor 1.7 (from 1.6)
• Migrating to Meteor 1.6 (from 1.5)
• Migrating to Meteor 1.5 (from 1.4)
• Migrating to Meteor 1.4 (from 1.3)
• Migrating to Meteor 1.3 (from 1.2)