Skip to content

Docs: erasableSyntaxOnly should mention type assertions #3465

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jakebailey merged 1 commit into from
Dec 2, 2025
Merged

Docs: erasableSyntaxOnly should mention type assertions #3465

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions packages/tsconfig-reference/copy/en/options/erasableSyntaxOnly.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ That means the following constructs are not supported:
* `namespace`s and `module`s with runtime code
* parameter properties in classes
* Non-ECMAScript `import =` and `export =` assignments
* `<prefix>`-style type assertions

```ts
// ❌ error: An `import ... = require(...)` alias
Expand Down Expand Up @@ -43,6 +44,9 @@ enum Direction {
Left,
Right,
}

// ❌ error: <prefix>-style type assertion.
const num = <number>1;
```

Similar tools like [ts-blank-space](https://github.com/bloomberg/ts-blank-space) or [Amaro](https://github.com/nodejs/amaro) (the underlying library for type-stripping in Node.js) have the same limitations.
Expand Down