Chris Krycho

Whether or not the host environment supports ESM, it should be straightforward to provide a standard bit of boilerplate to make bundling it into a version which handles module scopes...

This fell off my radar until I was doing a triage pass, but it pairs nicely with #876; I'm going to bring it to Framework this week. For good or...

We talked about this today at Framework, and rather than pushing this direction (and deprecating things piecemeal) we are going to FCP to close—by getting rid of it holistically as...

We shipped types from Ember itself, so this is no longer an issue. 🎉

This was superseded by the Octane programming model, where arguments are separate from the backing class properties. 🎉

Long since resolved by fixing type declarations in DefinitelyTyped and – more importantly – publishing types from Ember’s source.

Resolved by shipping types natively from Ember in `ember-source` v5.1.

Resolved by using [expect-type](https://www.npmjs.com/package/expect-type) to write *much* more robust type tests in Ember’s own published types.

As far as I can tell, this remains an issue on the TS side, but is largely irrelevant since every use of `this.get()` and `this.set()` in Ember can be safely...

Resolved via shipping native types from source in Ember 5.1 🎉