When building Ember components, you might have realised that there are two separate ways to interact with the component lifecycle
: either via hook methods, or lifecycle events. Although both APIs have been supported consistently for a long time, many learning resources (including the official Ember Guides) emphasized the usage of the hook methods
over the event-driven approach. To make the Component API more consistent and solidify the recommended convention, an RFC (Request for Comments) proposes deprecating the Component’s lifecycle event
API in favor of using hooks intstead.This RFC is open to your comments and suggestions
Can you name a few ways to slim down the Ember bundle in 3.0? By dropping support for IE9 and IE10
in Ember 3.x, some legacy tooling could be removed! For example, the Ember.Logger
util allowed a consistent debugging experience for Ember developers throughout the 1.x and 2.x era of the framework - the days of IE9 and 10. A new RFC proposes the deprecation of this logger util
that is no longer necessary. You can read more about the change and leave your comments to the proposal here.
The quest issue to make jQuery optional
in Ember and reduce overall bundle size of the framework made further progress through the refactoring of several more package tests (1
). This issue tracks important prep work for the current RFC. Developers will be able to opt-in to continue bundling jQuery into their vendor.js file when building their app through Ember CLI. The design for how to opt in/out of jQuery in its final comment period- so hurry, suggest and comment before it’s too late
Contributors this week were busy preparing bug fixes (2
) and doing lots of other cleanup and refactoring work (4
And finally, the historic ember-starter-kit
has been archived to become a read-only repository. Check out the repo to remind you of those sweet days when Ember CLI
didn’t have your back yet and you had to build up, scaffold and wire up your modules yourself, in the snow, uphill both ways.