Skip to content

doc: TypeScript docs should recommend erasableSyntaxOnly #57271

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
merged 2 commits into from
Mar 4, 2025
Merged

doc: TypeScript docs should recommend erasableSyntaxOnly #57271

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7231855
doc: recommend `erasableSyntaxOnly` in ts docs
robpalme Mar 2, 2025
aad965e
Remove allowImportingTsExtensions - it's implied
robpalme Mar 2, 2025
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: 2 additions & 2 deletions doc/api/typescript.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,15 +76,15 @@ generation, and by replacing inline types with whitespace, Node.js can run
TypeScript code without the need for source maps.

Type stripping is compatible with most versions of TypeScript
but we recommend version 5.7 or newer with the following `tsconfig.json` settings:
but we recommend version 5.8 or newer with the following `tsconfig.json` settings:

```json
{
"compilerOptions": {
"target": "esnext",
"module": "nodenext",
"allowImportingTsExtensions": true,
"rewriteRelativeImportExtensions": true,
"erasableSyntaxOnly": true,
"verbatimModuleSyntax": true
}
}
Expand Down
Loading