Ember 3.0 ships in less than a week! Stay tuned for links to the release blog post, instructions on how to upgrade, and more.
If you work on cleaning up any deprecations you see in your app today, the upgrade path will be straightforward. Developers who want to take full advantage of 3.0 but keep some deprecated methods around will have some options, too!
In regards to this week's Request for Comments (RFC)
news, the proposal to make jQuery
for Ember apps and therefore reducing overall minimal bundle size has been finalized and merged
. This means that after discussions with the community the RFC, is now ready for implementation.
Ember contributors are busy working on internal refactors that will unlock breaking up
more Ember features into packages
. The more modular the Ember codebase is, the greater the opportunity for tree shaking and smaller build bundles. Internal refactors includes less reliance on globals (1
) and removing the use of require (1
The Ember API documentation
is also due for some updates (1
). The content you see at https://www.emberjs.com/api
is extracted from code comment blocks in the Ember.js codebase itself.
Additionally, progress is being made
towards being able to use ES Classes
in Ember, as proposed in RFC-240
There are also some bugs resolved this week, like using the get template helper on arrays, some work on Backburner
, and testing fixes (1
), as well as further cleanup and refactoring work (1