Ember 2.16-LTS, Ember 2.17 and 2.18 Beta Released

Updated on December 19, 2017 to include information about Ember.js 2.16-LTS.

Today the Ember project is releasing Ember.js 2.16 LTS (a long-term support release) and version 2.17.0 of Ember.js, Ember Data, and Ember CLI.

This release also kicks off the 2.18 beta cycle for all sub-projects. We encourage our community (especially addon authors) to help test these beta builds and report any bugs before they are published as a final release in six weeks' time. The ember-try addon is a great way to continuously test your projects against the latest Ember releases.

Despite an initial delay on these releases, and an additional delay on this announcement, the Ember 3.0 Release Schedule is unchanged. This means that Ember 2.18 and the first beta of Ember 3.0 will be release on January 1st, 2018.

You can read more about our general release process here:


Ember.js is the core framework for building ambitious web applications.

Ember.js 2.16-LTS

Ember 2.16-LTS is the latest long-term support release. You can install it by upgrading ember-source to ~2.16.2 in your package.json.

The LTS channel is designed for Ember users who would like to upgrade less frequently, while still getting support from the project and the wider ecosystem. At the same time, it allows addon authors to know which versions of Ember to focus their effort on.

Per our usual policy, Ember 2.16-LTS is released six weeks after the 2.16.0 stable release. This allows ample time to fix any reported regressions and ensures a rock solid LTS release. It will continue to receive critical bugfixes for six release cycles (roughly August 2018), and security patches for ten release cycles (roughly Janurary 2019).

Meanwhile, Ember 2.12-LTS will continue to receive critical bugfixes for another two release cycles (roughly Feburary 2018), and security patches for six release cycles (roughly August 2018). Users of Ember 2.12-LTS should make use of this overlapping period to transition over to Ember 2.16-LTS.

For more details on the changes landing in Ember.js 2.16-LTS, please review the Ember.js 2.16.2 CHANGELOG.

Changes in Ember.js 2.17

Ember.js 2.17 is an incremental, backwards compatible release of Ember with bugfixes and performance improvements.

Some of the more notorious fixes were:

Deprecations in Ember 2.17

There were no new deprecations introduced in 2.17.

For more details on changes in Ember.js 2.17, please review the Ember.js 2.17.0 release page.

Upcoming Changes in Ember.js 2.18

Ember.js 2.18 will see the removal of the router.router deprecations and respective code.

Deprecations in Ember.js 2.18

One new deprecation was introduced in Ember.js 2.18:

For more details on the upcoming changes in Ember.js 2.18, please review the Ember.js 2.18.0-beta.1 and Ember.js 2.18.0-beta.2 release pages.

Ember Data

Ember Data is the official data persistence library for Ember.js applications.

Changes in Ember Data 2.17

Ember.js 2.17 will contain no new features. The changes introduced in Ember Data 2.17 mostly focus on bug fixes, improved documentation and build improvments to support changes in the ember-cli ecosystem and fix a regression in support for build using Node 4.x.

Deprecations in Ember Data 2.17

No new deprecations are introduced in Ember Data 2.17.

For more details on changes in Ember Data 2.17, please review the Ember Data 2.17.0 release page.

Upcoming changes in Ember Data 2.18

No major new features are planned for Ember Data 2.18. The Ember Data 2.18 is expected to focus on bug fixes around relationships. Some of the bigger bug fixes are expected to be backported to older releases durring the 2.18 beta cycle.

Deprecations in Ember Data 2.18

No new deprecations are planned in Ember Data 2.18.

For more details on the upcoming changes in Ember Data 2.18, please review the Ember Data 2.18.0-beta.1 release page.

Ember CLI

Ember CLI is the command line interface for managing and packaging Ember.js applications.

Upgrading Ember CLI

You may upgrade Ember CLI separately from Ember.js and Ember Data! To upgrade your projects using yarn run:

yarn upgrade ember-cli

To upgrade your projects using npm run:

npm install --save-dev ember-cli

After running the upgrade command run ember init inside of the project directory to apply the blueprint changes. You can preview those changes for applications and addons.

Changes in Ember CLI 2.17

Ember CLI previously displayed a warning when you removed ember-cli-shims, but the dependency is no longer needed if none of your dependencies are using the old shims and all of them are using ember-cli-babel 6.6.0 or above. Due to that, the warning has been removed in the new release.

With the release of Ember 2.17, Ember 2.16 becomes an LTS release. To ensure that the default ember-try configurations are up to date for new applications, Ember 2.8 LTS was retired from the configuration and Ember 2.16 was added.

Ember CLI has been using headless Chrome for ember test for a while. In Ember CLI 2.17 you now have the option to run your tests in a browser window using ember test --server.

Node.js 9 Support

Per the Ember CLI Node.js version support policy, Ember CLI officially supports Node 9 as the active Node.js version and will continue to do so throught its Active window.

As part of this support, Ember CLI will no longer report warnings when run under Node 9.

Node 7 will report warnings as its support period has terminated.

Other Notable Changes

  • The build pipeline went through an internal refactoring to make it more flexible and composable.
  • Fixed bug where the app/ tree was being linted even if it was not present.
  • Ensured test-support and addon-test-support trees are linted.

Deprecations in Ember CLI 2.17

No new deprecations were added in Ember CLI 2.17.

Upcoming Changes in Ember CLI 2.18

The next version of Ember CLI will see some user experience improvements.

crossdomain.xml will no longer be generated for new applications. The file was an artifact from a time when Flash was a popular vector for security exploits. Now that that is no longer a concern, the file is not necessary.

The livereload URL was removed from the output of ember server. Users would get confused because this URL is printed right away when running the development server, but the actual URL the application is running under will only be shown when the build is finished. Users would click the livereload URL and be greeted with a blank page and errors.

If you used npm link with a dependency that had itself npm link dependencies, they would be silently dropped in previous versions of Ember CLI. This is now addressed.

Deprecations in Ember CLI 2.18

There are no deprecations planned for Ember CLI 2.18.

For more details on the changes in Ember CLI 2.18.0-beta.1 and detailed upgrade instructions, please review the Ember CLI 2.18.0-beta.1 release page.

Thank You!

As a community-driven open-source project with an ambitious scope, each of these releases serve as a reminder that the Ember project would not have been possible without your continued support. We are extremely grateful to our contributors for their efforts.

comments powered by Disqus