Node Target Mapping
Orta Therox edited this page Jan 5, 2022
·
7 revisions
Pages 61
User documentation
News
Debugging TypeScript
- Performance
- Performance-Tracing
- Debugging-Language-Service-in-VS-Code
- Getting-logs-from-TS-Server-in-VS-Code
- JavaScript-Language-Service-in-Visual-Studio
- Providing-Visual-Studio-Repro-Steps
Contributing to TypeScript
- Contributing to TypeScript
- TypeScript Design Goals
- Coding Guidelines
- Useful Links for TypeScript Issue Management
- Writing Good Design Proposals
- Compiler Repo Notes
- Deployment
Building Tools for TypeScript
- Architectural Overview
- Using the Compiler API
- Using the Language Service API
- Standalone Server (tsserver)
- Dev Mode in Visual Studio
- TypeScript MSBuild In Depth
- Debugging Language Service in VS Code
- Writing a Language Service Plugin
- Docker Quickstart
FAQs
The Main Repo
Clone this wiki locally
Recommended Node TSConfig settings
You can let TypeScript compile as little as possible by knowing what the baseline support for ECMAScript features are available in your node version
You can also use https://github.com/tsconfig/bases/ to find tsconfig.json
s to extend, simplifying your own JSON files to just the options for your project.
To update this file, you can use node.green to map to the different options in microsoft/typescript@src/lib
Node 16
{
"compilerOptions": {
"lib": ["ES2021"],
"module": "commonjs",
"target": "ES2021"
}
}
Node 14
{
"compilerOptions": {
"lib": ["ES2020"],
"module": "commonjs",
"target": "ES2020"
}
}
Node 12
{
"compilerOptions": {
"lib": ["ES2019"],
"module": "commonjs",
"target": "ES2019"
}
}
Node 10
{
"compilerOptions": {
"lib": ["es2018"],
"module": "commonjs",
"target": "es2018"
}
}
Note: Follow issue #20411 for more information on changes to the es2018 target/lib.
Node 8
{
"compilerOptions": {
"lib": ["es2017"],
"module": "commonjs",
"target": "es2017"
}
}