Ember 4.1 Released

– By Jared Galanis

Today the Ember project is releasing version 4.1 of Ember.js, Ember Data, and Ember CLI.

This release kicks off the 4.2 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 is the core framework for building ambitious web applications.

Changes in Ember.js 4.1

Ember.js 4.1 is an incremental, backwards compatible release of Ember with bug fixes, performance improvements, and minor deprecations.

Bug Fixes

Ember.js 4.1 introduced 2 bug fixes.

  1. Passing an ObjectProxy to isEmpty with a property size now throws an assertion (#17570).
  2. The router has been updated so that when query params are using a nested value a Route can determine if that nested query param is marked as refreshModel. (#18269)


Ember.js 4.1 introduced 3 features.

  1. There's now a service export available from @ember/service in favor of the previously used inject, which was previously typically aliased upon import to service. (#19776)
  2. A refresh method has been added to the RouterService that calls refresh on all currently active routes, or if a route name is provided, refreshes only that route provided and its descendants. (#19471 / #19834)
  3. A @cached decorator for memoizing the result of a getter based on autotracking has been added to help when a getter is expensive and used very often. (#19772 / #19826)


Ember.js 4.1 introduced 1 deprecation.

  1. The AutoLocation class, which previously served to support detection of browser support for the History Location API is now deprecated. Virtually all browsers now support the history API, so this is what 'auto' will resolve to in almost every case, rendering the AutoLocation class unnecessary. Instead, please set locationType in config/environment.js to 'history'. (#19510)

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 4.1, please review the Ember.js 4.1.0 release page.

Ember Data

Ember Data is the official data persistence library for Ember.js applications.

Changes in Ember Data 4.1

Bug Fixes

Ember Data 4.1 introduced 0 bug fixes.


Ember Data 4.1 introduced 0 features.


Ember Data 4.1 introduced 0 deprecations.

For more details on changes in Ember Data 4.1, please review the Ember Data 4.1.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 4.1

Bug Fixes

Ember CLI 4.1 introduced 0 bug fixes.


Ember CLI 4.1 introduced 0 features.


Ember CLI 4.1 introduced 0 deprecations.

For more details on the changes in Ember CLI 4.1 and detailed upgrade instructions, please review the Ember CLI 4.1.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.