Chris Krycho

I believe this has been resolved upstream long since; but in any case the goal will be to align with spec decorators (and will not be something fixed in a...

Extending the `TestContext` works fine where it is still needed: ```ts import { module, test } from 'qunit'; import { setupRenderingTest } from 'ember-qunit'; import { render, type TestContext }...

Ah, yep, just a copy-paste error; edited the original for future readers too!

Closing as resolved in TS 3.4. The learnings from this fed into our design of and Ember's own policy that it is not *required* to add any given TS version...

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 plugin configured as part of the v2 add-on build for add-ons, in conjunction...

This has largely been resolved by way of a few changes: 1. We improved the types in this space (esp. for RSVP’s `Promise` compatibility) over time as TS afforded it....

We've revisited our `tsconfig.json` and its source of truth also now lives at `@tsconfig/ember`. 🎉

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 plugin configured as part of the v2 add-on build for add-ons, in conjunction...

Recommended linting configuration is now (as of a few versions back in Ember and Ember CLI) built in out of the box via Ember's own blueprints when using `--typescript`. 🎉

We've moved this to FCP, intending to merge; @wycats is adding some notes on what we need to do to get it to Released and esp. Recommended.