Glimpse into the future of tree shaking in your Ember apps with a new addon! Also check out Ember 3.0 prep work and lots of Gimmer news. Here's a quick summary of what happened last week:
Also a Long Term Support (LTS) release bugfix landed this week, improving the handling for catching run-wrapped errors. You can read more about the fix in the detailed PR description. And finally, the settled test helper has been refactored, which allows to check for pending async operations, and a new util for validating error handlers has been added.
With the previous introduction of the bundler and the broccoli-assembler in Ember CLI, the way has been paved with features to allow a more flexible build pipeline. One of these features, called tree shaking, will allow you to get rid of unused code in your application and build more lightweight assets. You can read more about the motivation behind this in the original RFC.
This week, the new ember-cli-tree-shakeraddonhas been released, which allows you to test out the future of tree-shaking in Ember today. Although the project is a work in progress, it already allows you to eliminate dead code in the addon tree and remove it from your application.
A huge thank you goes to @kellyselden and @twokul for creating both the RFC and the new addon.
The ember-cli-app-versionproject is a package that displays version data of your app in both the Ember Inspector and the app itself. Recent changes included avoiding errors to be thrown when the app’s configuration is not present (1, 2), a fix for the CI, and another dependency update.
This week, the way components are invoked has been refactored (1, 2), improvements to the handle table landed, and a static component helper for a more efficient component invocation has been introduced.
