Thanks to the great work that has been done by Ember's community, there are lots of new updates to be shared with you this week. Here's a short recap of what has been worked on in Glimmer, Ember, Fastboot, Ember Data and the learning resources and in the past days:
An interesting new RFC is opening up the discussion for dropping the support of certain legacy browsers in the future major release of Ember - v3.0. Empowering users, addon authors and Ember developers to rely on a more modern baseline of native browser features per default while developing, this RFC is aiming to improve the developer experience with and alongside the framework tremendously. Be sure to check out the discussion on GitHub to learn more about the motivation for this deprecation and how the future browser support matrix for Ember 3.0 might look like. Many thanks to @rwjblue for creating this important RFC.
Also this week the Ember.String deprecation RFC finally landed; it aims to deprecate String related prototype extensions and leads to the htmlSafe methods being moved to the @ember/template module. Many thanks again to @Serabe for working on this important RFC. Finally, a bug fix for range input values has landed this week, which you can check out here. Many thanks to @Serabe for working on this fix, too.
A lot of community effort has been put into Glimmer this week; first, an interesting new update allows Glimmer component templates to have more than a single root element. The new bounds property allows the definition of a "main" element inside of components where the former this.element syntax wouldn't apply. You can read more about this change in the PR which landed this week and many thanks to @tomdale for implementing this feature.
Further changes have landed in the Glimmer VM this week, including a small update for a better, internal module organization here, an update to make publishing @glimmer packages to npm more straightforward here and finally another change to allow in-element rehydration. If you would like to read more about the latter change, be sure to also check out the original PR here.