Skip to content

Commit 9b7cec5

Browse files
authored
Clarify paragraphs about setting up TS
1 parent c2dc8fa commit 9b7cec5

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

content/stable-typescript-types-in-ember-5-1.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,10 @@ This is all that is necessary to unlock autocomplete and in-editor documentation
4343

4444
### TypeScript
4545

46-
For a new TypeScript project, the setup is similar, but has some additional steps for now. In the future, these steps will not be necessary. For now, the default TypeScript blueprint continues to set up users for maximum backward compatibility with the rest of the Ember ecosystem.
46+
Using the stable types in a new TypeScript projects is similar to setting it up for JavaScript, but has a few additional steps. To provide maximum backward compatibility with the rest of the Ember ecosystem, the default TypeScript blueprint still uses the `@types` packages, and configures those packages to use Array prototype extensions. Both of these are incompatible with the stable types, so we need to remove them! In the future, once we can switch to defaulting to using the stable types in the default blueprint, these extra steps will not be necessary.
47+
48+
(For details on migrating *existing* Ember TypeScript projects, see the [Migration Guide](#toc_migration-guide) below as well.)
49+
4750

4851
First, in `types/<your-app>/index.d.ts`, you will likely have something like this:
4952

@@ -93,8 +96,6 @@ Finally, you will need to remove the following packages from your `package.json`
9396
- `@types/ember__test`
9497
- `@types/ember__utils`
9598

96-
For details on migrating existing Ember TypeScript projects, see the [Migration Guide](#toc_migration-guide) below!
97-
9899
That's all you need to do to enjoy the new TypeScript support!
99100

100101

0 commit comments

Comments
 (0)