Today the Ember project is releasing version 3.26 of Ember.js, Ember Data, and Ember CLI.
This release kicks off the 3.27 beta cycle for all sub-projects. We encourage our community (especially addon authors) to help test these beta builds and report any bugs before they are published as a final release in six weeks' time. The ember-try addon is a great way to continuously test your projects against the latest Ember releases.
You can read more about our general release process here:
Ember.js
Ember.js is the core framework for building ambitious web applications.
Changes in Ember.js 3.26
Ember.js 3.26 is an incremental, backwards compatible release of Ember with bug fixes, performance improvements, and minor deprecations.
Bug Fixes
Ember.js 3.26 introduced 5 bug fixes. Here are a few notable ones:
- The Ember router and the
router
service have been updated so that an infinite recursion does not occur when therouter
service is injected intoapp/router.js
. (#19405) - You can pass to an observer a dependent key whose name includes a colon. (#19343)
- The Glimmer VM has been updated to prevent eagerly consuming arguments during modifier destruction. (#19469)
Features
Ember.js 3.26 introduced 0 features.
Deprecations
Ember.js 3.26 introduced several deprecations in preparation for v4.0 release. To learn more how to update your code, please check the provided link to the Deprecations Guide.
- Transition methods of controllers and routes have been deprecated. Inject the
router
service and use the service's methods instead. (Deprecations Guide, #19255) - Invoking the
<LinkTo>
component with positional arguments has been deprecated. Please provide named arguments such as@route
,@model
,@models
, and@query
. (Deprecations Guide, #19345) - The
{{with}}
helper has been deprecated, in favor of using{{let}}
. (Deprecations Guide, #19346) - Implicit injection has been deprecated. In particular, the
store
service from Ember Data must be explicitly injected into controllers and routes if they refer tothis.store
. (Deprecations Guide, #19358) - Browser support of Internet Explorer 11 has been deprecated. (Deprecations Guide, #19359)
- Property fallback for implicit
this
has been deprecated. Please review the templates in your app and writethis.
when it is appropriate, e.g. change{{localProperty}}
to{{this.localProperty}}
. (Deprecations Guide, #19371) - Ember Classic has been deprecated. (Deprecations Guide, #19372)
In preparation for v4.0 release, developers are encouraged to update their app to Ember Octane by following these steps:
- In
config/optional-features.json
, update the feature flags for Octane.
{
"application-template-wrapper": false,
"jquery-integration": false,
"template-only-glimmer-components": true
}
- Specify the Octane edition in
package.json
.
{
"ember": {
"edition": "octane"
}
}
- Check the official upgrade guide and seek help in the
#help
channel on Ember Discord.
(list continued from above)
- Component managers that use the
v3.4
capabilities should update to the most recent component capabilities available, which is currentlyv3.13
. (Deprecations Guide, #19373) - Modifier managers that use the
v3.13
capabilities should update to the most recent modifier capabilities available, which is currentlyv3.22
. (Deprecations Guide, #19373) - The
{{hasBlock}}
and{{hasBlockParams}}
properties have been deprecated. Use{{has-block}}
and{{has-block-params}}
helpers instead. (Deprecations Guide, #19374) - Passing
classBinding
andclassNameBindings
as arguments has been deprecated. (Deprecations Guide, #19375) - Accessing named arguments via
{{attrs}}
has been deprecated. (Deprecations Guide, #19375) - Array observers have been deprecated. (Deprecations Guide, #19381)
Deprecations are added to Ember.js when an API will be removed at a later date. Each deprecation has an entry in the deprecation guide describing the migration path to a more stable API. Deprecated public APIs are not removed until a major release of the framework.
Consider using the ember-cli-deprecation-workflow addon if you would like to upgrade your application without immediately addressing deprecations.
For more details on changes in Ember.js 3.26, please review the Ember.js 3.26.0 release page.
Ember Data
Ember Data is the official data persistence library for Ember.js applications.
Changes in Ember Data 3.26
Bug Fixes
Ember Data 3.26 introduced 0 bug fixes.
Features
Ember Data 3.26 introduced 0 features.
Deprecations
Ember Data 3.26 introduced 0 deprecations.
For more details on changes in Ember Data 3.26, please review the
Ember Data 3.26.0 release page.
Ember CLI
Ember CLI is the command line interface for managing and packaging Ember.js applications.
Upgrading Ember CLI
You may upgrade Ember CLI using the ember-cli-update
project:
npx ember-cli-update
This utility will help you to update your app or addon to the latest Ember CLI version. You will probably encounter merge conflicts, in which the default behavior is to let you resolve conflicts on your own. For more information on the ember-cli-update
project, see the GitHub README.
While it is recommended to keep Ember CLI versions in sync with Ember and Ember Data, this is not required. After updating ember-cli, you can keep your current version(s) of Ember or Ember Data by editing package.json
to revert the changes to the lines containing ember-source
and ember-data
.
Changes in Ember CLI 3.26
Bug Fixes
Ember CLI 3.26 introduced 2 bug fixes.
- Issue a better error message for add-on's missing an entry point. (#9473); and
- Add Prettier files to
.npmignore
file in addon blueprint (#9437).
Features
Ember CLI 3.26 introduced 1 feature.
-
ember-try
test scenarios forembroider-safe
andembroider-optimized
for addons are now enabled using @embroider/test-setup allowing Embroider compatibility testing for addons test matrix (#9436).
Deprecations
Ember CLI 3.26 introduced 0 deprecations.
For more details on the changes in Ember CLI 3.26 and detailed upgrade
instructions, please review the Ember CLI 3.26.0 release page.
Thank You!
As a community-driven open-source project with an ambitious scope, each of these releases serves as a reminder that the Ember project would not have been possible without your continued support. We are extremely grateful to our contributors for their efforts.
Top comments (1)
It's interesting to read and analyze, thanks