DEV Community: Ember.js

Ember 3.28 and 4.0 Beta Released

Ember.js — Tue, 07 Sep 2021 18:30:42 +0000

After 3.5 years and 28 minor releases, Ember 3.28 marks the end of the project's 3.x series. To ensure a smooth upgrade path going into the 4.x series, 3.28 has been declared an LTS (Long Term Support) candidate. In six weeks, the latest patch version of 3.28 will be promoted to be the latest LTS release and replace 3.24-LTS.

We're also announcing the start of the Ember 4.0 beta cycle for all sub-projects. Following the process set in previous major versions, Ember 4.0's beta introduces no new features. Instead, it removes support for deprecated public APIs. We encourage our community (especially addon authors) to help test beta builds and report any bugs before they are published as a stable release in six weeks' time. We also encourage everyone to help maintainers resolve deprecations in their favorite addons. The ember-try addon is a great way to continuously test your projects against the latest Ember releases.

Developers who want to prepare for the upcoming 4.0 version of Ember should work to resolve all deprecation warnings in their apps and addons while using Ember 3.28. An app or addon with no deprecation warnings on Ember 3.28 should be able to upgrade from Ember 4.0 without making significant changes outside of the dependency versions.

You can read more about Ember's plans for 4.0 in The Road to Ember 4.0.

Ember.js

Ember.js is the core framework for building ambitious web applications.

Changes in Ember.js 3.28

Ember.js 3.28 is an incremental, backwards compatible release of Ember with bug fixes, performance improvements, and a minor deprecation fix. 3.28 introduces no new features, helping to ensure the final release of the 3.x cycle is stable and battle-tested.

For the full set of changes (including 7 bug fixes), see the Ember.js 3.28.0 release page on GitHub.

In Ember 3.24, various string methods added to the String.prototype were deprecated for removal in Ember 4.0. htmlSafe (the version available via string prototype) was supposed to be included in those deprecations, however it was overlooked. This omission is corrected in 3.28.

Ember Data

Ember Data is the official data persistence library for Ember.js applications. The changes introduced in Ember Data 3.28 focus on bug fixes and refactors in preparation for 4.0.

Changes in Ember Data 3.28

Improvements to relationship materialization & unloading performance

A number of performance improvements were shipped in Ember Data 3.28, including significant improvements to relationship materialization and unloading performance via emberjs/data#7491 and emberjs/data#7493. In particular, the performance improvements should be notable when loading large sets of data.

See the PRs linked above and changelog for further notes on performance improvements.

Unload records from the store when calling `destroyRecord`

destroyRecord would previously leave the deleted record in the store. This could cause issues if IDs were re-used, or could require extra filtering to confirm that destroyed content was not in an array of models.

3.28 will unload records from the store when destroyRecord is called. For more details, see emberjs/data#7258 and the GitHub issues mentioned in the PR.

Custom Model Classes

Used conventionally, Ember Data blends the definition of a model's schema and record API into a single JavaScript class. For example:

import Model from '@ember-data/model';

export default class PersonModel extends Model {
  /*
   * Define a schema
   */
  @attr('string') firstName;
  @attr('string') lastName;

  /*
   * Define an API on the record instance
   */
  get fullName() {
    return `${this.firstName} ${this.lastName}`;
  }
}

Ember Data 3.28 introduces the ability to separate model schema and record instance class definitions. This is a low-level capability that we expect addon authors to use when they experiment in these areas (possibly others):

First, forcing the definition (statically or at runtime) of a distinct class for every model can cause performance issues. Large applications may have hundreds of models. If most or all of these models do not require unique classes, we're generating more memory load and asking more of the JIT's type system than they may be necessary. In the extreme case, it may be possible for all record instances in an application to share a single root class.

Second, the current Ember Data schema definition API forces definitions to be authored in JavaScript. Removing that limitation allows us to experiment with more optimal or powerful ways to encode schema (such as JSON). These alternatives may perform better (in payload size, or in parse/eval), may better support generation and synchronization with API typing systems, and better support static analysis (for example, with TypeScript).

For further details on these new capabilities, refer to:

Much of this API surface is already used by the ember-m3 project, which provides an alternative model class for Ember Data.

Bug Fixes

Ember Data 3.28 introduced 12 bug fixes and some internal refactors. For the full set of changes, see the CHANGELOG.md.

Ember CLI

Ember CLI is the command line interface for managing and packaging Ember.js applications.

Changes in Ember CLI 3.28

Drop Node 10 support

Ember CLI 3.28 drops support for Node 10. Node 10 became end of life (it no longer receives security updates) in April 2021.

Introducing `ember-addon.projectRoot`

This new configuration option allows you to run ember serve from outside of a project's root directory. For example, if you're using yarn workspace or a monorepo and want to support running ember serve from the root of the repo, update the top-level package.json to include the following config:

{
  "ember-addon": {
    "projectRoot": "./packages/path-to-ember-project"
  }
}

For more details on the changes in Ember CLI 3.28 and detailed upgrade instructions, please review the Ember CLI 3.28.0 release page.

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.

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.

The Road to Ember 4.0

Ember.js — Thu, 15 Jul 2021 14:39:17 +0000

Contributors to the Ember project have been hard at work since Ember Octane was released in December 2019.

Over the duration of a challenging (and sometimes devastating) year and a half, we've shipped a powerful new feature (Named Blocks) and supported an ecosystem shifting to Octane conventions. We've more closely aligned Ember with wider frontend conventions through improved publishing & build tooling (Embroider) and better support for TypeScript (both through ember-cli-typescript and reducing reliance on type-unsafe framework features).

Announcing Ember 4.0

In his EmberConf 2021 keynote, Yehuda shared a name for Ember's next edition: Polaris. In order to unblock Polaris providing the best, most productive experience the Ember project can build, we're going to remove already-deprecated APIs in a 4.0 release.

Ember 3.27, which has already been released, was the final version of Ember to include new deprecations targeting Ember 4.0.

Ember 3.28, which has been released as a beta, will be released as stable around August 9th. It will not introduce additional deprecations targeting Ember 4.0. Six weeks after its stable release, around September 20th, Ember 3.28 will become a Long-Term Support release.

Ember 4.0 will be released around September 20th. Ember 4.0 itself is not an LTS candidate.

Ember 4.4 will be the first LTS candidate of the 4.x series. It will be released as stable around February 2022 and as an LTS around March 2022.

Whats in a 4.0?

Since the release of Ember 2.0, major versions of Ember have been about removal of deprecated API, and not about the introduction of new features or development styles. Ember 4.0 follows that tradition, and will contain no new features.

Additionally, Ember 4.0 does not remove the EmberComponent API or the core parts of the EmberObject system. These APIs are widely used, even after the release of Octane, by existing application and addon code.

Ember 4.0 will remove all APIs deprecated in Ember 3.x and targeting Ember 4.0. These include:

Ember.Logger is removed in favor of native console APIs. Guide here.
Copyable mixin is removed in favor of the ember-copy addon. Guide here.
sendAction is removed in favor of calling closure actions like any other callback. Guide here.
willTransition and didTransition are removed in favor of router service events. Guide here.
Computed Property volatile() calls are removed in favor of native getters. Guide here.
this.$() and other jQuery APIs are deprecated in favor of native browser equivalents. Guide here. An optional feature which restored this and other jQuery-specific features is also removed. Guide here.
{{partial}} is removed in favor of template-only components. Guide here.
Using the built-in global resolver (App.FooController anyone?) is deprecated in favor of using ember-resolver, already the default for Ember CLI generated apps. Guide here.
Ambiguous references to a component's properties are removed. You must now write {{this.someProp}}. Guide here.
renderTemplate is removed in favor of {{in-element}} or other rendering target redirection like ember-wormhole. Guide here.
Support for the Ember global on window is removed in favor of importing the Ember object or using the module-based API. Guide here.
Support for specific features of the <LinkTo>, <Input>, and <Textarea> components are removed. See guides on positional arguments, legacy arguments, legacy HTML attributes, and importing legacy built-in components.
Finally, Ember classic is deprecated in favor of Ember Octane. Although many APIs from Ember classic (like EmberComponent) continue to be available, the optional features and application configuration which define Ember Octane must be enabled in 4.0. See the deprecation guide entry and upgrading to Ember Octane guide for more details.

The above APIs, listed as an example of what will be removed but not defining the complete list, show that API removals in 4.x largely consist of APIs that date back to Ember 1.x, and are rarely used now (or should be rarely used).

An additional important change is the completion of Ember 3.x's browser support policy. Ember 4.0 will support two classes of browsers: Evergreen (those on a weeks-long, auto-upgrade release cycle) and non-evergreen. This classification system allows us to create a rolling minimum version for evergreen browsers, while using a more traditional, pinned minimum version for non-evergreen browsers.

Specifically, the Ember 4.x release policy includes support for Google Chrome, Mozilla Firefox, Microsoft Edge, and Apple Safari on desktop and mobile. It does not include support for any version of Internet Explorer.

Read more about this change in the deprecation guide and at Ember's browser support policy page.

Existing Ember users should note that Ember 3.27 has already removed IE11 from the default target list for production and testing builds.

Planning your upgrade to 4.0

For each API removed in Ember 4.0, you can find an entry in the Ember 3.x deprecation guide. As many of the removed APIs have not been included in best practices or common documentation for the entire 3.x cycle, applications started on 3.x are expected to have a fairly smooth upgrade path.

Consider using the ember-cli-deprecation-workflow addon as part of your upgrade process. The addon allows you to create a configuration file to silence most deprecations. This means you can focus on one or a few warnings at a time. Additionally, you can configure the addon to throw an error when a deprecation that was previously addressed is re-introduced. If you work with a large codebase and many contributors, this helps you prevent backsliding in your upgrade process.

In contrast to prior major releases, we have no plans to offer an ember-3-legacy package that makes Ember 3.x APIs available for a limited time in Ember 4.0. This is based on fairly low use of these packages in the past.

Don't panic. We expect many Ember users to enthusiastically adopt our 4.0 release. If you prefer a conservative upgrade path, we suggest using Ember's Long-Term Support releases. Ember 3.28, the last version of the 3.x cycle, will become an LTS in September 2021. The first 4.x release to be promoted to LTS will be Ember 4.4 around March 2022. This timeline provides a long window for your business to address any remaining 4.0-targeted deprecations (while using 3.28-LTS) before 4.4-LTS is promoted.

Contributing to Ember 4.0

In the Ember.js, Ember Data, and Ember CLI repos, the final beta cycle of 3.x has already started. The master branch is ready for code changes targeting 4.0. You are welcome to contribute to these repos by removing already deprecated functionality and IE11 compatibility code.

The core framework effort to prepare for 4.0 is tracked at emberjs/ember.js#19545, and a list of deprecated APIs we need help to remove is tracked at emberjs/ember.js#19617.

Join us on Discord in the #dev-ember-js, #dev-ember-data, #dev-ember-cli, or #dev-ember-learning channels to find out how you can contribute.

In less than six weeks, we expect the first betas for 4.0 to be released. Please help test the betas on your applications and addons so that we can catch any regressions.

We're looking forward to working with the community on Ember 4.0 and on the opportunities beyond it. As always we appreciate your support, your trust, and our common partnership.

Ember 3.27 Released

Ember.js — Thu, 15 Jul 2021 03:42:58 +0000

On July 3, 2021, the Ember project announced release 3.27 of Ember.js, Ember Data, and Ember CLI. This is a minor version, stable release.

We also announced the start of the 3.28 beta cycle for all sub-projects. We encourage our community (especially addon authors) to help test beta builds and report any bugs before they are published as a stable release in six weeks' time. The ember-try addon is a great way to continuously test your projects against the latest Ember releases.

Ember.js 3.28 (again, starting beta today) is the final planned version of the 3.x release cycle, and will become an LTS release. As of the 3.28-beta being released, the main development branch of all Ember projects will become 4.0. Look for more information on Ember 4.0 here on the blog this coming week.

You can read more about our general release process with these resources:

Ember.js

Ember.js is the core framework for building ambitious web applications.

Changes in Ember.js 3.27

Ember.js 3.27 is an incremental, backwards compatible release of Ember with bug fixes, performance improvements, and deprecations. For a full set of changes see CHANGELOG.md.

Notable Bug Fixes

Prior to 3.27 <:inverse> would not always alias else blocks. This is corrected in glimmerjs/glimmer-vm#1296.
Ember.js 3.27.0 was released in early May and included several regressions. These were largely related to the changes in the glimmer VM and and the implementation of several deprecations, and have been corrected in patch releases leading up to 3.27.5.

Feature Additions

Contextual Helpers & Modifiers

For several years Ember has provided a mechanism called "contextual components". This API allows a developer to yield a component, optionally with arguments to apply, into a block.

In RFC #432 additional APIs were proposed which allow helpers and modifiers to be used in the same way.

For example the layout for a SuperForm component might be implemented as:

// app/components/super-form.hbs
<form>
  {{yield (hash

    Input=(component "super-input" form=this model=this.model)
    Textarea=(component "super-textarea" form=this model=this.model)
    Submit=(component "super-submit" form=this model=this.model)

    is-valid=(helper "super-is-valid" form=this model=this.model)
    error-for=(helper "super-error-for" form=this model=this.model)

    auto-resize=(modifier "super-auto-resize")

  )}}
</form>

And be used as:

// app/templates/index.hbs
<SuperForm @model={{this.post}} as |f|>

  {{! Invoke a contextual component }}
  <f.Input @name="title" />

  {{! Invoke contextual helpers }}
  {{#unless (f.is-valid "title")}}
    <div class="error">This field {{f.error-for "title"}}</div>
  {{/unless}}

  {{! Invoke a contextual modifier on a contextual component invocation }}
  <f.Textarea @name="body" {{f.auto-resize maxHeight="500"}} />

  <f.Submit />
</SuperForm>

These APIs open the doors for the creation of new, more powerful UI abstractions.

Deprecations

Ember 3.27 introduces the final set of deprecations targeting Ember 4.0. The newly introduced deprecations primarily impact uncommonly used APIs. As always, deprecated APIs are documented with a transition path in the deprecation guides.

Several notable deprecations added in 3.27 are:

Invoking Helpers Without Arguments and Parentheses in Named Argument Positions

In some templates, a helper passed as an argument can be treated as an invocation instead of passing the uninvoked helper as a value. For example:

{{! is someHelper invoked, or passed as a reference? }}
<SomeComponent @arg={{someHelper}} />

To better align helpers with how component and modifiers behave in the same setting, parenthesis are now required to cause an invocation:

{{! (someHelper) is clearly an invocation with no arguments }}
<SomeComponent @arg={{(someHelper)}} />

The non-param version of helper passing will pass a reference to the helper in Ember 4.0. See the deprecation guide entry for more details.

Importing Legacy Built-in Components

Historically, Ember applications have been able to import the base classes which define <Input>, <Textarea>, and <LinkTo> for reopening or subclassing. In Ember 4.0, we intend to improve the internal implementation of those built-ins. To allow this, we've been steadily deprecating parts of the built-in APIs throughout the 3.x release series.

In 3.27, importing a the base classes of Ember built-ins is deprecated. In Ember 4.0 these modules will be unavailable. The specific deprecated imports are:

import Checkbox from '@ember/component/checkbox';
import Textarea from '@ember/component/text-area';
import TextField from '@ember/component/text-field';
import LinkToComponent from '@ember/routing/link-component';

Accessing these classes through other paths, like the owner interface, is also deprecated.

See the deprecation guide entry for more details and guidance on migrating away from these APIs.

Additionally, reopening these classes (for example to change the tagName on a <LinkTo>) has been deprecated and will be unsupported in 4.0. See the deprecation guide for migration strategies.

Deprecate Legacy Arguments to Built-ins

Ember's built-in components had a public interface largely defined by their implementation as classic Ember components. In order to refactor these built-ins to more modern implementations and improve their interfaces, large parts of their API is deprecated in 3.27.

These deprecations break down into two sections. First, there are arguments which are essentially setting HTML attributes or dealing with events. See this guide entry on legacy attribute arguments for a detailed list of deprecated arguments and migration paths.

Second, there is a set of arguments which were effectively leaks of the private implementation, or which no longer have a clear meaning (or usefulness) in modern application development. See this guide entry on legacy arguments for a detailed list and migration paths.

Deprecate the Ember Global

Ember has long set a property on the window or globalThis global so that it can be accessed via window.Ember, for example. This approach to using Ember is incompatible with static analysis tools that can result in more optimized application payloads.

In Ember 3.27, accessing the Ember object via a non-module-import is deprecated. Support for using Ember this way will be removed in Ember 4.0.

Instead, applications should adopt the Ember module API. This means importing either the Ember object or a specific API from the module API:

// Bad, deprecated
export default Ember.Component.extend({});

// Better
import Ember from 'ember';
export default Ember.Component.extend({});

// Best
import Component from '@ember/component';
export default Component.extend({});

See the deprecation guide and RFC 706 for more details and transition paths for other use cases.

Further Information On Upgrade Timelines

For application maintainers who want to upgrade apps to Ember.js 4.0 on its release date, the list of deprecations in this release means their challenge is now well defined. Application maintainers should consider using the ember-cli-deprecation-workflow addon to address deprecations incrementally after upgrading to 3.27. ember-cli-deprecation-workflow 2.0 was released today in preperation for applications addressing Ember 3.x deprecations. Give us feedback in the issues on that repo.

For app maintainers who are in less of a hurry, please note that the upcoming release of Ember.js 3.28 will contain no new deprecations targeting Ember.js 4.0. Additionally, Ember.js 3.28 will be promoted to LTS on the same day Ember.js 4.0 is released.

We recommend that applications using LTS releases wait for the first LTS of Ember.js 4.x to upgrade, which will be Ember.js 4.4. Ember's 6 week release cycle means we expect there is about 44 weeks (from today) for apps upgrading from LTS-to-LTS to address 4.0-targeted deprecations before Ember.js 4.4-LTS is made available.

For more details on changes in Ember.js 3.27, please review the Ember.js 3.27.5 release page.

Ember Data

Ember Data is the official data persistence library for Ember.js applications. Ember Data's 3.27 release largely consists of compatability work with Ember.js.

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

Changes in Ember CLI 3.27

Ember CLI 3.27 introduces a flag for enabling Embroider (Ember CLI's new build pipeline) for new applications and addons. For example:

ember new my-app --embroider

Learn more about what Embroider offers and how to best configure it on the embroider-build/embroider repo.

For more details on changes and bugfixes in Ember CLI 3.27, see the Ember 3.27.0 changelog and Ember CLI 3.27.0 release page.

Thank You!

Ember 3.26 Released

Ember.js — Mon, 12 Apr 2021 19:34:53 +0000

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 the router service is injected into app/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 to this.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 write this. 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 currently v3.13. (Deprecations Guide, #19373)
Modifier managers that use the v3.13 capabilities should update to the most recent modifier capabilities available, which is currently v3.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 and classNameBindings 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

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 for embroider-safe and embroider-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!

Ember 3.25 Released

Ember.js — Fri, 26 Feb 2021 06:44:59 +0000

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

This release kicks off the 3.26 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.25

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

Bug Fixes

Ember.js 3.25 contains several bug fixes, including:

Empty hmtmlSafe strings are now considered false. (#18148)
Template locals no longer clobber component invocations of the same name. (#19351)
Improved error message when invoking nested components, e.g. <Foo:Bar />. (#19336)
Improved error messages and stack traces for <LinkTo />. (#19342)

Features

Ember.js 3.25 introduced 2 features.

Template strict mode (#19302, #19306, #19319)

While this feature won't have an impact for Ember developers quite yet, it is an important step towards allowing more experimental work in templates, like template imports and single-file components.

If these topics interest you, keep an eye on our RFCs repository for activity and a chance to participate!

Named blocks (#19318)

This feature enables developers to yield distinct blocks from a component, unlocking powerful composition patterns for components.

This feature is useful when you want to render different things depending on passed-in data.
Let us implement a shopping cart that lists the items in it, or shows a message that says it is empty.
We will be using {{gt}} from ember-truth-helpers to help implement this.

First we write the component template:

// app/components/cart.hbs
{{#if (gt @list.length 0)}}
  <ul>
    {{#each @list as |item|}}
      <li>{{yield item}}</li>
    {{/each}}
  </ul>
{{else}}
  {{yield to="empty"}}
{{/if}}

Which can be used like so:

<Cart @list={{this.shoppingList}}>
  <:default as |listItem|>
    <p>You have a {{listItem}}.</p>
  </:default>
  <:empty>
    <p>Your cart is empty.</p>
  </:empty>
</Cart>

Then when shoppingList contains multiple elements, like [ "apple", "pear", "banana" ], it renders the following:

<ul>
  <li><p>apple</p</li>
  <li><p>pear</p</li>
  <li><p>banana</p</li>
</ul>

But if shoppingList is empty, it renders the following instead:

<p>Your cart is empty.</p>

Named blocks are also useful if you want to ensure a certain structure to your HTML, but want to enable customization of the content.
An example of this would be an <Article> component, as shown in the yieldable named blocks RFC (#460).

You can find more information in the Component API documentation.

Deprecations

Ember.js 3.25 introduced 0 deprecations.

For more details on changes in Ember.js 3.25, please review the Ember.js 3.25.0 release page.

Ember Data

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

Changes in Ember Data 3.25

Apart from documentation fixes and internal cleanup of feature flags, there were no changes.

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

Changes in Ember CLI 3.25

Apart from updated dependencies in the app and addon blueprints, there were no changes.

For more details on the changes in Ember CLI 3.25 and detailed upgrade
instructions, please review the Ember CLI 3.25.0 release page.

Thank You!

Ember 3.24 Released

Ember.js — Thu, 07 Jan 2021 19:28:09 +0000

Today the Ember project is releasing version 3.24 of Ember.js, Ember Data, and Ember CLI. This release of Ember.js is an LTS (Long Term Support) candidate. LTS candidates prioritize stability over the addition of new features, and have an extended support schedule.

This release kicks off the 3.25 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.24

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

Bug Fixes

Ember.js 3.24 introduced 4 bug fixes.

When the router service is injected (e.g. into a component), the router service can automatically work in non-application tests. In other words, we no longer need to call this.owner.setupRouter(). (#19080)
When there is no template associated with a component class, the low-level API getComponentTemplate() now returns undefined instead of null. The return value of undefined is what had been specified in the Component Templates Colocation RFC. (#19253)
In an Ember Engines app, the <LinkTo> component once again supports linking within an engine. Please note, a fix was made possible through a breaking change in the private implementation of <LinkTo>. When you upgrade your app to v3.24 or above, you will want to upgrade Ember Engines to at least ember-engines@0.8.9 (see release notes here for details). (#19223) ⚠️
When a computed property has a dependent key that includes @each, followed by an aliased property, the computed property recomputes when the aliased property's value changes. (#19280)

Features

Ember.js 3.24 introduced 3 features.

When ember-page-title is installed, the blueprint for a route template creates a {{page-title}} helper invocation in addition to {{outlet}}. For more information, please see RFC #645 and ember-page-title documentation. (#19224)
The interface of DeprecationOptions, which can be passed to the deprecate() function, requires the keys for and since to exist. For more information, please see the Deprecation Staging RFC. (#19133)
Glimmer VM, the rendering engine, has been upgraded to version 0.65.0. The upgrade includes a bug fix and a few upstreams. (#19258, #19261, #19267)

Deprecations

Ember.js 3.24 introduced 4 deprecations.

Going back to the interface of DeprecationOptions (see Features above), forgetting to pass for or since will trigger a deprecation message. (#19133)
Ember.String.loc function, @ember/string#loc function, and {{loc}} helper have been deprecated in favor of a dedicated localization solution like ember-intl. For more information, please see the Deprecations Guide. (#19211)
Calling camelize, capitalize, classify, dasherize, decamelize, underscore, or w—these are Ember.String methods—on a string is deprecated. Instead of calling the method on the string, you can import the function from @ember/string:

// Before
let mascot = 'Empress Zoey';

console.log(mascot.camelize());  // empressZoey

// After
import { camelize } from '@ember/string';

let mascot = 'Empress Zoey';

console.log(camelize(mascot));  // empressZoey

For more information, please see the Deprecations Guide. (#19234)

tryInvoke from @ember/utils module has been deprecated in favor of JavaScript's optional chaining ?..

// Before
import { tryInvoke } from '@ember/utils';

let today = new Date('01/07/2021');

tryInvoke(today, 'getTime');              // 1609974000000
tryInvoke(today, 'setFullYear', [2014]);  // 1389049200000
tryInvoke(today, 'noSuchMethod', [2014]); // undefined

// After
let today = new Date('01/07/2021');

today.getTime?.();          // 1609974000000
today.setFullYear?.(2014);  // 1389049200000
today.noSuchMethod?.(2014); // undefined

/*
  Note, `today` is used in the context of `tryInvoke`.
  As a result, we can assume that `today` is an object
  and write `today.getTime` instead of `today?.getTime`.

  The examples exist only to illustrate how to refactor
  `tryInvoke`. Please don't write `today.getTime?.()`
  in practice. :)
*/

For more information, please see the Deprecations Guide.

Consider using the ember-cli-deprecation-workflow addon if you would like to upgrade your application without immediately addressing deprecations.

Last but not least, Ember.js 3.24 removed a few feature flags and an experimental API called expandLocalLookup. For more details on changes in Ember.js 3.24, please review the Ember.js 3.24.0 release page.

Ember Data

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

Changes in Ember Data 3.24

Bug Fixes

Ember Data 3.24 introduced 1 bug fix.

In a production environment, an attempt to set something on a deleted record no longer shows the value in the error message. This was done to prevent leaking sensitive data. (#7370)

Features

Ember Data 3.24 introduced 0 features.

Deprecations

Ember Data 3.24 introduced 0 deprecations.

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

Changes in Ember CLI 3.24

Bug Fixes

Ember CLI 3.24 introduced 1 bug fix.

When Embroider v2 addons are present, prevent forming a cycle in the build process. (#9402)

Features

Ember CLI 3.24 upgraded the packages that are present in the package.json blueprint to their latest version. There are 4 notable changes to the package.json blueprint:

ember-page-title has been added to the blueprint. For more information, please see RFC #645 and ember-page-title documentation. (#9372, #9382)
ember-qunit has been upgraded to v5 (a major version change). Following the migration guide, the package.json blueprint includes @ember/test-helpers and qunit. The blueprints for tests/index.html and tests/test-helper.js have been updated as well. (#9340, #9371)
eslint-plugin-ember has been upgraded to v10 (a major version change), which promoted octane rules to recommended and enabled several additional rules as recommended. To learn more about these linting rules, please check the eslint-plugin-ember documentation. (#9403)
prettier (along with eslint-config-prettier and eslint-plugin-prettier) has been added to the blueprint. To learn more, please see RFC #628 and Prettier documentation. (#9391, #9407, #9410)

Deprecations

Ember CLI 3.24 introduced 0 deprecations.

For more details on the changes in Ember CLI 3.24 and detailed upgrade
instructions, please review the Ember CLI 3.24.0 release page.

Thank You!

Ember 3.23 Released

Ember.js — Tue, 15 Dec 2020 03:33:11 +0000

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

This release kicks off the 3.24 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.23

Ember.js 3.23 is an incremental, backwards compatible release of Ember with bugfixes, performance improvements, and minor deprecations.

Ember.js 3.23 introduced several bug fixes, including:

Updated Glimmer (rendering engine) to improve developer experience with debugging (#19213)
Ensured that (fn (mut ...)) works with falsy values (#19221)
Fixed bugs in query parameters with intermediate transitions (#19249)
Prevented multiple serialization of query parameters on activeTransition (#19236)
Prevented dynamic invocation of string value when referenced directly in angle brackets (#19122)
Issued a deprecation for tracked mutation in constructor during rendering (#19282) ⚠️

New Features

Ember.js 3.23 introduced 2 features.

Implemented and enabled invokeHelper from JavaScript Helper Invocation API RFC. The invokeHelper can be used to create and call an instance of the helper in a component. (#19171, #19182)
Implemented and enabled helper manager from Helper Managers RFC. It provides a low-level primitive for defining helpers. (#19160, #19182)

Deprecations

Ember.js 3.23 introduced 0 deprecations.

For more details on changes in Ember.js 3.23, please review the Ember.js 3.23.0 release page.

Ember Data

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

Changes in Ember Data 3.23

This release included several bug fixes and improvements, such as:

Improved debug message (#7337).
Polymorphic relation type changes on first load (#7363).

Deprecations (1)

najax when ember-fetch is also a dependency

Building on the deprecation of the previous minor version, #7230 also triggers a deprecation warning when ember-fetch is installed to better guide users on how to update their app.
You can consult the Deprecate najax request deprecation guide for more information.

For more details on changes in Ember Data 3.23, please review the
Ember Data 3.23.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 easily using the ember-cli-update project:

npx ember-cli-update

Changes in Ember CLI 3.23

No significant changes were introduced in this version of Ember CLI.
Upcoming changes to how the blueprint for new applications sets up testing were delayed to next minor version due to regressions.

For more details on the changes in Ember CLI 3.23 and detailed upgrade
instructions, please review the Ember CLI 3.23.0 release page.

Thank You!

Ember 3.22 Released

Ember.js — Tue, 20 Oct 2020 14:19:34 +0000

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

This release kicks off the 3.23 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.22

Ember.js 3.22 is an incremental, backwards compatible release of Ember with bugfixes, performance improvements, and minor deprecations.

Ember.js 3.22 introduced several bug fixes, including:

RouterService#isActive updates correctly when the route changes. (#19094)
A custom modifier manager only consumes arguments that it actually uses. (Previously, the manager would eagerly consume all arguments.) In order for specific modifiers to take advantage of this change, they need to call modifierCapabilities('3.22') (instead of '3.13'). (#19163)
Modifier manager accepts the resolved value of owner.factoryFor directly. This approach aligns with how helpers and component managers work. (#19170)
Changes made to protocolForUrl (in 3.22.0-beta.2+) work in fastboot@3.1.0 environment by leveraging the native JavaScript URL global. (#19124)

New Features

Ember.js 3.22 introduced 3 features.

Enabled @ember/destroyable API, which allows you to create and manage your own destroyables. For more information, please see the Destroyables RFC.
Enabled Cache API, a low-level primitive for memoizing the result of a function based on autotracking. (You can install a polyfill for apps between versions 3.13 and 3.21.) For more information, please check the Ember Guides and Autotracking Memoization RFC.
Allowed passing the transition object to 2 route hooks, activate and deactivate.

Deprecations

Ember.js 3.22 introduced 0 deprecations.

Ember Data

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

Changes in Ember Data 3.22

Ember Data 3.22 included several bug fixes of note, including:

several fixes ensuring that the Errors.errorsFor array and subarray are properly updated and that autotracking works #7273, #7330, and #7331;
#7322 disables the esm cache to solve build time errors some applications were experiencing; and
#7126 addresses relationship state when sideposting with lid.

New Features

Ember Data 3.22 introduced 0 features.

Deprecations

Ember Data 3.22 introduced 1 deprecation.

Use of najax has been deprecated in favor of ember-fetch when FastBoot is installed. To learn how to migrate your app, please see the Deprecations Guide.

For more details on changes in Ember Data 3.22, please review the
Ember Data 3.22.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 easily using the ember-cli-update project:

npx ember-cli-update

Changes in Ember CLI 3.22

Ember CLI 3.22 includes only internal changes. However, please note that eslint-plugin-ember released a new major version, v9.x. The new version introduces 6 recommended rules and removes support of Node v13.

New Ember apps will install v9 or higher of eslint-plugin-ember, which may limit the version of Node that you use. To learn more, please check out the changelog for eslint-plugin-ember.

New Features

Ember CLI 3.22 introduced 0 features.

Deprecations

Ember CLI 3.22 introduced 0 deprecations.

For more details on the changes in Ember CLI 3.22 and detailed upgrade
instructions, please review the Ember CLI 3.22.0 release page.

Thank You!

Hacktoberfest 2020

Ember.js — Thu, 01 Oct 2020 16:41:58 +0000

Have you ever spotted something in Ember code or documentation that needed fixing? Did you want to get involved in contributing to open source, but you have no idea where to start?

Good news! It's Hacktoberfest 2020, and you are invited to participate in Ember-focused special events and mentorship opportunities through the month of October. You can make some commits, meet some new people, and maybe get some free stuff!

What is Hacktoberfest?

Hacktoberfest is an annual, worldwide celebration organized by DigitalOcean and sponsored by many companies that use open source software.

The premise is simple:

Sign up anytime between October 1 and October 31
Make 4 valid Pull Requests to any public repositories on GitHub
If you are among the first 70,000 developers who complete the challenge, you get a prize. This year, you can select between a T-shirt and a tree planted in your name.

Many open source project maintainers put in some extra effort during Hacktoberfest to make it easy and fun to participate in open source.

What is happening in the Ember community?

Here's what you can expect this year!

On Saturday, October 10th, past contributors will be available to pair with anyone who wants to help out! If you have questions or need some help finding an issue to work on, this is a great place to start. Specific times will be announced soon.
On Friday, October 16th, there will be an Ember Contributors Workshop! Tickets are sold out but you can read more about the event on the EmberFest website.
At any time, join the #hacktoberfest channel in the Ember Community Discord to connect with other developers. You can find a buddy to pair with, a mentor to guide you, or toss around ideas.

If you are someone who is willing to help mentor new contributors, please let us know in #hacktoberfest on Discord. Addon maintainers are welcome to post issues they need help with too!

Additionally, there are several more groups within the Ember Community Discord where you can find others to collaborate with. There are Discord channels for women, LGBTQ+, and people of color. If you belong to one of those groups, you can ask to join in the #discord-server-admin channel.

How do I choose what to work on?

It all depends on your interests! One of the best ways to get involved in open source is to pick up a teeny tiny issue so you can learn the flow and what to expect. Then, consider making an improvement to something you regularly use; for example, a feature, test, or fix to API documentation.

For ideas, you can visit Ember's Help Wanted. The Ember Learning Team and others are curating some super beginner-friendly issues. In Help Wanted, you can find these issues, along with more intermediate and advanced issues. If you want to help, comment on an issue to let others know that you are working on it. If the issue you want to work on is taken, try asking if the other volunteers would like to collaborate!

Can I participate if I am not working on Ember things?

Absolutely! Hacktoberfest is a celebration for all open source projects. Ember is just one of many.

Ember 3.21 Released

Ember.js — Wed, 02 Sep 2020 16:21:51 +0000

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

Version 3.20 of Ember is now promoted to LTS (Long Term Support). An LTS version of Ember continues to receive security updates for 9 release cycles (54 weeks) and bugfixes for 6 cycles (36 weeks). LTS releases typically occur every four minor versions. The previous LTS version of Ember was 3.16.

This release kicks off the 3.22 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.21

Ember.js 3.21 is an incremental, backwards compatible release of Ember with bugfixes, performance improvements, and minor deprecations.

New Features

Ember.js 3.21 introduced no new features.

Deprecations

Ember.js 3.21 introduced 1 deprecation.

getWithDefault (both the function and class method) has been deprecated per RFC #554.

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

Ember Data

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

Changes in Ember Data 3.21

Ember Data 3.21 release saw a few improvements to documentation and continuous integration.

New Features

Ember Data 3.21 introduced no new features.

Deprecations

Ember Data 3.21 introduced no deprecations.

For more details on changes in Ember Data 3.21, please review the
Ember Data 3.21.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 easily using the ember-cli-update project:

npx ember-cli-update

Changes in Ember CLI 3.21

New Features

Ember CLI 3.21 introduced 2 new features.

ember new --lang support has landed per RFC #635.
ember-try configuration for addons has been updated. ember-lts-3.12 has been dropped from the default testing matrix. (Existing addons should consider this as a breaking change.) In addition, ember-lts-3.20 has been added to the default testing matrix.

Deprecations

Ember CLI 3.21 introduced no deprecations.

For more details on the changes in Ember CLI 3.21 and detailed upgrade
instructions, please review the Ember CLI 3.21.0 release page.

Thank You!

Accessibility Working Group Update

Ember.js — Wed, 26 Aug 2020 00:09:00 +0000

Back in March, an Accessibility (A11y) Strike Team was formed to address the issues outlined in Ember RFC Issue 595 - Technical Accessibility Issues in New Ember Apps. This blog post is to update the community on that group's work.

The Strike Team met weekly between March 25 and June 24. We even managed to celebrate Global Accessibility Awareness Day!

There were five items listed in Issue 595:

Application Language Support
Label/Input Support
Page Title Support
Support for ...attributes
Accessible Routing Support

Active Work

Application Language Support

The goal of application language support was to provide a mechanism for new Ember apps to pass WCAG Success Criteria 3.1.1 - Language of Page. To meet that goal, Joseph Sumner, Jamie White, Ava Wroten and Melanie Sumner authored RFC 635, which proposed a --lang flag for ember-cli. This flag would enable developers to declare the application's language while they were creating the app, allowing them to more easily meet this particular success criteria. This RFC was merged on June 12th; the feature itself, authored by Joseph Sumner with help from Rob Jackson, was merged on August 24th.

To add another layer of support and enhance the overall developer experience, the team also decided that it would be useful to have an interactive way to create new Ember apps. After some discussion, Melanie Sumner authored RFC 638. The RFC was accepted and merged on August 10th. Implementation is still pending.

Additional support came from update to the Ember Guides, in both prose and art, thanks to team members Ava Wroten and Lenora Porter. Melanie Sumner also added a new rule to the Ember Template Lint addon called require-lang. It checks to make sure that the lang attribute is present on the <html> attribute. This rule will be effective in v3.0 of the addon, thanks to Alex Kanunnikov adding the ability to lint .html files in PR 1232.

Label and Input Support

There were 3 things the team decided to do in this area:

Update the guides to provide more explicit guidance
Provide an addon that would help provide ids within a specific context
Write an RFC to propose a more permanent solution

Benjamin Jegard created the Ember Context Id Helper addon. The {{context-id}} generates a unique id for a given context. Because it uses Ember's guidFor function under the hood, it will always return the same id for the same context. A use case for context-id helper is to programmatically associate <label>s and <input> element using the <label> for attribute and the <input>s id attribute.

This addon took inspiration from the pre-RFC for the guid-for helper, which resulted in RFC 659, which proposes a new built-in template helper, authored by Steve Szczecina.

Rajasegar Chandran and Jen Weber updated the Official Ember Guides with more explicit information for how to associate <label> and <input> elements. Melanie Sumner also authored ember-component-patterns that reflect best practices for <input> fields.

Finally, support has been added to the Ember Template Lint addon with rules that require <input> elements to have valid labels and that there are no duplicate labels. Additional work is now being done to check that there are no duplicate ids as well as valid use of form groups.

Page Title Support

In our April 8th meeting, the team discussed how we thought we should approach page title support. More discussion throughout the month led us to support the template-driven support for page titles in Ember apps.

Benjamin Jegard, Melanie Sumner and Ricardo Mendes authored RFC 645, which proposes that the Ember Page Title addon be added to the blueprints for new Ember apps. After Framework Core Team discussion, it was decided that the addon needed some work before the RFC could be accepted. That work was outlined in an issue and is currently underway, thanks to community member Raido Kuli!

Back to the Drawing Board

After discussion and some analysis, it was determined that some issues required the attention of the Framework Core Team to resolve. These issues will likely require re-thinking of significant Ember features, so some workarounds should be expected until they are resolved.

Support for `...attributes`

As outlined in Ember Issue 19026, ...attributes does not have a guaranteed merge order. This is problematic for 5 ARIA attributes because they can have multiple values in the form of an ID reference list and the order of these values matters.

This is likely to lead to some additional discussion about how Ember handles properties and attributes, and rethinking that approach to better support attributes.

Accessible Routing

There is an ongoing discussion for how to best resolve this issue in a permanent way. Despite a significant amount of research into the issue and an RFC that attempts to solve the issue, no resolution has been agreed upon yet. However, the Framework Core Team has accepted that accessibility is a design constraint for any new router work.

Until then, developers are encouraged to review the accessibility section of the Ember guides, and consider one of the routing-related addons for use. Options include ember-self-focused, a11y-announcer, ember-a11y, and ember-a11y-refocus.

A11y Working Group

At the final Strike Team meeting, we decided to continue the accessibility work in Ember and became the Ember A11y Working Group. We coordinate in the #dev-ember-a11y channel on Ember's Discord server and meet as needed. Anyone who is interested is welcome to join in!

Work is also underway to upscale the addons in the Ember-A11y GitHub org! We are also continuing to add first-class accessibility support to ember-template-lint; coming soon is support for users to be able to specifically only run the accessibility-related linting rules on a codebase.

Thank You

A huge thank you to all of the community members who participated in the Ember A11y Strike Team: Abhilash Ramesh, Amy Lam, Ava Wroten, Benjamin Jegard, Emmanuel Patrick, Eric Kelly, Frédéric Soumaré, Jamie White, Jen Weber, John Costanzo, Joseph Sumner, Lennex Zinyando, Lenora Porter, Melanie Sumner, Praskovia Root, Rajasegar Chandran, Robert Jackson, Steve Szczecina, and Seema Shariat.

Ember 3.20 Released

Ember.js — Thu, 30 Jul 2020 15:23:31 +0000

Today the Ember project is releasing version 3.20 of Ember.js, Ember Data, and Ember CLI. This release of Ember.js is an LTS (Long Term Support) candidate. LTS candidates prioritize stability over the addition of new features, and have an extended support schedule.

This release kicks off the 3.21 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.20

Ember.js 3.20 is an incremental, backwards compatible release of Ember with bugfixes, performance improvements, and minor deprecations.

Developers who upgrade their Ember apps to v3.20 should also update @glimmer/component to v1.0.1 to avoid a deprecation warning that comes from the @glimmer/component package's use of a private API.

New Features (1)

`{{in-element}}`

Have you ever wished you could render a component somewhere outside of the usual HTML flow? To help with this, Ember.js now provides the {{in-element}} helper as public API. If you have used community addons like ember-wormhole or ember-elsewhere, you are probably familiar with the challenge that {{in-element}} aims to solve.

To use the helper, pass in a DOM element to target (this.myDestinationElement in the example below) and a block to render:

{{#in-element this.myDestinationElement}}
  <div>Some content</div>
{{/in-element}}

This new public API behaves a little differently from the private API:

For the public API {{in-element}}, by default, the rendered content will replace all the content of the destination, effectively becoming its innerHTML. If you want it to be appended instead of replacing the content, you can pass in insertBefore=null.
In the private API {{-in-element}}, the rendered content was appended to any existing content in the destination.

Developers should use the public API, {{in-element}}, and discontinue using {{-in-element}}.

See RFC 287 for more information about the motivation for this new feature.

Deprecations (1)

`Meta.prototype.setSourceDestroyed` and `Meta.prototype.setSourceDestroying`

Previous versions of the @glimmer/component package relied on this intimate API, which is now deprecated.
To resolve deprecation warnings in your own apps and addons, update your version of @glimmer/component to at least v1.0.1.

Deprecations are added to Ember.js when an API will be removed at a later date. Each public API 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.20, please review the Ember.js 3.20.0 release page.

Ember Data

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

Changes in Ember Data 3.20

In addition to a new feature, this release also includes some performance optimizations for visiting relating records and updating has-many relationships.

New Features (1)

`isEmbeddedRecordsMixinCompatible`

Previously, if you used the EmbeddedRecordsMixin and JSONAPISerializer together, the app would show a warning that this combination did not work.
However, some developers may have APIs that would have theoretically been compatible.
For those use cases, you can now set this.isEmbeddedRecordsMixinCompatible = true in the serializer, and you will no longer see the warning.

For apps that mistakenly use the EmbeddedRecordsMixin and JSONAPISerializer together, without setting the boolean, the app will now assert instead of warn.

Deprecations (0)

No new deprecations introduced in Ember Data 3.20.

For more details on changes in Ember Data 3.20, please review the
Ember Data 3.20.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 easily using the ember-cli-update project:

npx ember-cli-update

Changes in Ember CLI 3.20

New Features (1)

Syncing Blueprints

Apps and addons can update the ember-cli version in their app without impacting future ember-cli-update runs.

Before this new feature, ember-cli-update used the current version of ember-cli in the package.json to determine which version to attempt to update from. Unfortunately, that meant that if you were to update your ember-cli version without also running the full blueprint update, you would have a much harder time updating your general project structure in the future.

See the Syncing Blueprints RFC to learn more about the motivation and design of this feature!

Deprecations (2)

Usage on Node 13 will now issue a warning
Usage of the PACKAGER experiment is deprecated. This only affects apps that opted into setting the EMBER_CLI_PACKAGER environment variable.

For more details on the changes in Ember CLI 3.20 and detailed upgrade
instructions, please review the Ember CLI 3.20.0 release page.

DEV Community: Ember.js

Ember 3.28 and 4.0 Beta Released

Ember.js

Changes in Ember.js 3.28

Ember Data

Changes in Ember Data 3.28

Improvements to relationship materialization & unloading performance

Unload records from the store when calling destroyRecord

Custom Model Classes

Bug Fixes

Ember CLI

Changes in Ember CLI 3.28

Drop Node 10 support

Introducing ember-addon.projectRoot

Upgrading Ember CLI

Thank You!

The Road to Ember 4.0

Announcing Ember 4.0

Whats in a 4.0?

Planning your upgrade to 4.0

Contributing to Ember 4.0

Ember 3.27 Released

Ember.js

Changes in Ember.js 3.27

Notable Bug Fixes

Feature Additions

Contextual Helpers & Modifiers

Deprecations

Invoking Helpers Without Arguments and Parentheses in Named Argument Positions

Importing Legacy Built-in Components

Deprecate Legacy Arguments to Built-ins

Deprecate the Ember Global

Further Information On Upgrade Timelines

Ember Data

Ember CLI

Upgrading Ember CLI

Changes in Ember CLI 3.27

Thank You!

Ember 3.26 Released

Ember.js

Changes in Ember.js 3.26

Bug Fixes

Features

Deprecations

Ember Data

Changes in Ember Data 3.26

Bug Fixes

Features

Deprecations

Ember CLI

Upgrading Ember CLI

Changes in Ember CLI 3.26

Bug Fixes

Features

Deprecations

Thank You!

Ember 3.25 Released

Ember.js

Changes in Ember.js 3.25

Bug Fixes

Features

Deprecations

Ember Data

Changes in Ember Data 3.25

Ember CLI

Upgrading Ember CLI

Changes in Ember CLI 3.25

Thank You!

Ember 3.24 Released

Ember.js

Changes in Ember.js 3.24

Bug Fixes

Features

Deprecations

Ember Data

Changes in Ember Data 3.24

Bug Fixes

Features

Deprecations

Ember CLI

Unload records from the store when calling `destroyRecord`

Introducing `ember-addon.projectRoot`

Support for `...attributes`

`{{in-element}}`

`Meta.prototype.setSourceDestroyed` and `Meta.prototype.setSourceDestroying`