Ember 3.0: Nothing says let’s celebrate like tidying up the framework
Honestly, it’s a rather refreshing approach to the release cycle. So, let’s see what needs to be thrown in the trash this year!
Let’s start off with the basics: Ember 3.0 doesn’t have any new functionality. No shiny new features, no nifty new tools. Ember is the same as it always has been since the last release.
Well, mostly. Instead, Ember 3.0 is focusing on the functionality and performance of the framework by cutting out extraneous and unnecessary APIs. But, the team at Ember isn’t stopping anything too dramatically; any APIs marked for depreciation have been frozen since July 2017.
Builds of Ember and Ember Data for use with a
<script> tag are no longer published as of 3.0. This includes:
- Builds published to Bower as
- Builds published to S3, for example at
- Builds published to CDNs, for example at
Instead applications should make Ember a dependency via NPM or Yarn:
ember-sourceis the Ember NPM package.
ember-datais the Ember Data NPM package.
So, what else got chopped? Ember drops support for Internet Explorer 9, IE 10, and PhantomJS. More dead weight for the garbage collectors includes a number of APIs. Here are some of the big ones:
- Function as test in
- Ember debug function options
- And more
Have a look at the full depreciation guide to keep track of everything going off to the dump.
Other changes to Ember 3.0
Most of the big changes in this release are bug fixes and cleaning away dead weight. That being said, there are some updates to be aware of.
Additionally, in Ember 3.0 reading a computed property without using
get will cause an assertion failure in development. This will help applications correct their currently incorrect usage.
There are also some changes to Ember Data 3.0 and Ember CLI 3.0 other than the now-traditional API depreciations. Ember Data 3.0 contains small bug fixes and updated test generators for the new testing APIs. Ember CLI 3.0 makes it easier to use
await by including the addon ember-maybe-import-regenerator in the default app blueprint.
How popular is Ember, anyways?
As we discussed previously on JAXenter, it’s pretty well known that choosing a framework is a matter of personal opinion and taste. Whether or not Ember moves forward relies entirely on the community. And as long as people are happy with using Ember, it’ll keep trucking on.
Migrating to Ember 3.0
To make sure that as many applications as possible survive the transition from 2.x to 3.x, all public APIs removed in Ember 3.0 have been extracted into the ember-2-legacy add-on. This add-on will be supported through Ember.js 3.4, the first LTS of the 3.x series.