Chris Krycho

This was resolved via a series of workarounds (hacks? But of a respectable variety!) in ember-concurrency. Thanks for the original reports, folks!

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...

This should have been resolved by shipping types natively from Ember. If someone happens across this and finds that it is not, please file a bug on Ember itself!

I believe this is not an ember-cli-typescript specific issue, but in any case we now recommend that people switch to using `ember-cli-babel` for apps (as documented [here](https://github.com/babel/ember-cli-babel#enabling-typescript-transpilation)) and the rollup...

Ember's own types do their best here, but there's a reason we deprecated the array prototype extensions. Net, this is no longer an active issue, and folks should stick to...

`ember-cli-typescript` itself works fine with Yarn (and nom and pnpm) workspaces and has since v2. Additionally, we now recommend that people switch to using `ember-cli-babel` and running `glint` or `tsc`...

Resolved by Ember shipping its own types. 🎉

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

FWIW, I've confirmed this issue does not exist with Ember's [own types][source] *or* the latest version of [the types on DefinitelyTyped][DT], so I'm going to mark this issue as *closed*,...

We've tweaked this to a spot we're all happy with – regardless of whether it exactly matches what anyone proposed here!