| title | author | tags |
|---|---|---|
Ember 2.18 and 3.0 Beta Released |
Ricardo Mendes |
Releases |
Today the Ember project is releasing version 2.18.0 of Ember.js, Ember Data, and Ember CLI.
This release kicks off the 3.0 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.
After 2.5 years and 18 minor releases, Ember 2.18 marks the end of the 2.x series. As the last release in the series, 2.18 is an LTS candidate to ensure a smooth upgrade path going into the 3.x series.
You can see the full release schedule up to 3.5 in “The Road to Ember 3.0”.
You can read more about our general release process here:
Ember.js is the core framework for building ambitious web applications.
Ember.js 2.18 is an incremental, backwards compatible release of Ember with bugfixes, performance improvements, and minor deprecations.
Ember 2.18 does not introduce new deprecations.
For more details on changes in Ember.js 2.18, please review the Ember.js 2.18.0 release page.
Ember.js 3.0 represents the first release in the 3,0 series. Repeating what happened in the previous cycle, Ember 3.0 will remove a number of public APIs.
Some developers might still be relying on some of these removed APIs. To enable these developers to upgrade piecemeal, we have created the ember=2=legacy addon.
The ember-2-legacy addon will enable developers to selectively opt into continuing to use removed APIs until a time when they can migrate away from them.
Developers should reference the 2.x series deprecation guide to see which pieces of public API will be removed in 3.x and how to migrate.
Public APIs to be removed in 3.0 are as follows:
didInitAttrsis removed and can be replaced withinit- One form of declaring an
observerwhere dependent keys are stated after the callback (they should go before the callback as described in the API docs) - Enumerable and Array
containsshould be replaced withincludes - Providing
{{link-to}}with a param wrapped in a controller - Specifying
defaultLayoutto a component, rather than layout - Using
Ember.Handlebars.SafeStringinstead ofEmber.String.htmlSafe Ember.Kshould be replaced with inline functions
The Ember 3.x series will also drop support for Internet Explorer 9 and 10. Earlier this year, Microsoft announced end of life for these browser versions, ending their own technical and security updates.
No new deprecations are introduced in Ember.js 3.0.
For more details on the upcoming changes in Ember.js 3.0, please review the Ember.js 3.0.0-beta.1 release page.
Ember Data is the official data persistence library for Ember.js applications.
One new deprecation is introduced in Ember Data 2.18:
- Support for "production-like" values of
EMBER_ENVwill be removed. For example, custom production names likeproduction-qashould be replaced withproduction
For more details on changes in Ember Data 2.18, please review the Ember Data 2.18.0 release page.
For more details on the upcoming changes in Ember Data 3.0, please review the Ember Data 3.0.0-beta.1 release page.
Ember CLI is the command line interface for managing and packaging Ember.js applications.
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.
Ember CLI 2.18 is an incremental release, featuring bugfixes and improvements.
According to the Node.js support policy of the Ember CLI project, Node 7 is removed from the testing matrix. If you are developing an application using Ember CLI, it is recommended that you upgrade your Node to one of the active LTS versions to guarantee security updates.
Previously, if you were npm-linking an addon that had itself npm-linked a dependency, Ember CLI would fail to find it. This is now fixed.
crossdomain.xml was originally introduced to limit vulnerabilities with using the Flash Player,
by declaring which servers it could connect to outside the one currently hosting it.
Browsers have since disabled Flash for security reasons, rendering the file moot.
Ember CLI 2.18 will no longer generate the file when generating new applications.
- #7443 Use overrides for a single .eslintrc.js. @rwjblue
- #7455 Add eslint-plugin-ember to default linting config. @rwjblue
I guess the biggest user-facing change is the ESLint thing. We now only have a single .eslintrc.js file and that includes eslint-plugin-ember by default.
Ember CLI 2.18 does not introduce new deprecations
For more details on the changes in Ember CLI 2.18 and detailed upgrade instructions, please review the Ember CLI 2.18.0 release page.
Ember CLI 3.0 will feature a much improved README for the addon blueprint. The improvements include:
- An automatically generated "Installation" section
- An empty "Usage" section
- A "License" section
- Setext headings to emphasize sections when in raw text mode.
Ember CLI 3.0 does not introduce new deprecations.
For more details on the changes in Ember CLI 3.0.0-beta.1 and detailed upgrade instructions, please review the Ember CLI 3.0.0-beta.1 release page.
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.