Edward Faulkner

Note from RFC review: reminder that this is hard to remove without also removing classic component, because of the `click` support etc.

Let's make it clear that this RFC also effectively amends the earlier tracked storage primitives RFC to say that that one (which has no official implementation anyway) got superseded by...

At RFC review we discussed whether we really need `Cell.prototype.set`, since assignment of `current` means the same thing. It's true that closing over assignment in our templates is not currently...

We need to think through what this would mean for ember-cli-update. Because deprecating and removing the feature for newly generated apps is one thing, whereas forcing it on existing apps...

Discussion notes from RFC review: Since we don't envision removing this feature for existing apps (no reason to force them to change package managers), this isn't strictly a normal deprecation....

This is an older RFC from before we started tracking RFC stages and I realized it's not implemented, so I bumped it back from "recommended" to "accepted". There's a high-quality...

Examples of content that should go into the release documentation page: - the cadence of majors - that no new features go into majors - that we turn the prior...

Implementation projects: - ember-auto-import needs a relatively small feature - @embroider/vite: vite doesn't have out of the box support for import.meta.resolve but has the right semantics on `new URL(..., import.meta.url)`,...

> @ef4 could you elaborate what that small feature would be? Are you saying we don't need the full webpack implementation as in https://github.com/webpack/webpack/issues/16693? Having proper upstream support like that...

The runtime template compiler is not subject to the same limitations as the ahead-of-time template compiler. There's no reason all of it needs to go through `new Function(...)`. And we...