When this is disabled, it will make Ember CLI's build process not include jQuery into the vendor.js bundle, and it will explicitly put Ember itself into its "no jQuery" mode.

This RFC defines a new package format that is designed to make Ember packages (meaning both apps and addons) statically analyzable and more compatible with the rest of the NPM & …

This RFC defines a new app format, building off the prior work in v2 Addon format, and is designed to make Ember apps more compatible with the rest of the JavaScript ecosystem.

Oct 19, 2018 · If there are changes to the spec, and it is possible to avoid changing the public APIs of decorators, then Ember will make the changes necessary to avoid public API changes.

The focus of this RFC is not to write new content, but make better use of what is already there by presenting it in a different order. We aim to rearrange the table of contents without breaking …

Those convenient methods increase the likelihood of becoming potential roadblocks for future built-in language extensions, and make it confusing for users to onboard: is it specifically part …

For example, we could make a scoreboard component that keeps score for an arbitrary number of players, and keep track of the score for each player using tracked version of JavaScript Map.

You can use the sync option to make them asynchronous instead and convert them over time. You can also enable the default-async-observers optional feature to make them asynchronous …

I'm not convinced we could make it work at reasonable cost in even all current build systems, never mind future ones. As written, this RFC has low-risk of causing compatibility problems in …

While we may introduce new decorator primitives in the near future, iterating on the existing decorators to make them stricter in largely painless ways will allow more teams to migrate to a …