What's new in TypeScript 7.0: a 10x faster native compiler, new defaults, and more
TypeScript 7.0 doesn't change how you write TypeScript, but it changes how long you wait for it.
TypeScript 7.0 was officially released on July 8, 2026. It's the release the TypeScript team has been working toward for over a year: a native port of the compiler and language server, written in Go, that typically builds projects 8 to 12 times faster than TypeScript 6.0.
Unlike TypeScript 5.0, which introduced decorators, const type parameters, and other language features, TypeScript 7.0 is mostly about speed. TypeScript 7.0 doesn't change how you write TypeScript, but it changes how long you wait for it. It also turns on a set of new defaults that TypeScript 6.0 prepared, removes long-deprecated options, and ships without the JavaScript compiler API that some tools rely on.
In this article, you'll explore what changed in TypeScript 7.0, what breaks when you upgrade, and how to move your project over.
Getting started with TypeScript 7.0#
TypeScript 7.0 ships under the same typescript package on npm, and the compiler is still called tsc. Run the following command in your project's directory to install it:
npm install -D typescriptThen check the version:
npx tsc -vYou should see:
Version 7.0.2If you're using an older project, your package.json probably pins a 5.x or 6.x version range, so update it to ^7.0.2 before you install.
What's new in TypeScript 7.0?#
Let's go through the changes, starting with the one that motivated the whole release.
A native compiler that's about 10x faster#
Until TypeScript 6.0, the compiler was written in TypeScript and ran on Node.js. For TypeScript 7.0, the team ported the compiler and the language service to Go. Go compiles to native code and lets the compiler type-check files on several threads at once, which the JavaScript version couldn't do.
The port keeps the same type-checking behavior. The TypeScript team says that code that compiles cleanly on TypeScript 6.0 (with the stableTypeOrdering option on and no ignoreDeprecations setting) should compile identically in TypeScript 7.0.
Here are the full build times the TypeScript team measured on large open-source projects, with TypeScript 7.0's default settings:
| Project | TypeScript 6.0 | TypeScript 7.0 | Speedup |
|---|---|---|---|
| VS Code | 125.7s | 10.6s | 11.9x |
| Sentry | 139.8s | 15.7s | 8.9x |
| Bluesky | 24.3s | 2.8s | 8.7x |
| Playwright | 12.8s | 1.47s | 8.7x |
| tldraw | 11.2s | 1.46s | 7.7x |
Memory usage went down too, by between 6% (Sentry) and 26% (Bluesky) in the same benchmark.
These numbers come from the TypeScript team's own benchmark, so your project's speedup will depend on its size and structure. The team also shared results from companies that tested TypeScript 7.0 early: Slack's CI type-checking went from about 7.5 minutes to 1.25 minutes.
Parallel type-checking with --checkers and --builders#
The new compiler type-checks a project with several checkers running in parallel. By default, it uses four. You can change that with the new --checkers flag:
npx tsc --checkers 8With eight checkers, the VS Code build in the benchmark above dropped further, from 10.6 seconds to 7.51 seconds. More checkers use more memory and CPU cores, so the right number depends on your machine.
If your repository uses project references, the new --builders flag sets how many projects are built at the same time:
npx tsc --build --builders 4And if you need the old behavior, for example, in a CI runner with a single CPU core, use --singleThreaded:
npx tsc --singleThreadedA faster editor experience#
The language service, which powers autocompletion, error highlighting, and go-to-definition in your editor, was also ported to Go and now runs on the Language Server Protocol (LSP).
The difference is most noticeable in large codebases. In the VS Code codebase, opening a file with an error and seeing that error took about 17.5 seconds with TypeScript 6.0 and under 1.3 seconds with TypeScript 7.0.
At launch, you enable it in VS Code by installing the TypeScript Native Preview extension. Once installed, it becomes the default. If you run into problems, run Disable TypeScript 7 Language Server from the Command Palette to switch back. The TypeScript team said support would also ship as part of VS Code itself, so check the TypeScript blog for the current setup.
The --watch mode was rebuilt too. It now uses a file watcher based on Parcel's watcher, ported to Go.
New defaults in your tsconfig.json#
TypeScript 6.0 was a bridge release. It deprecated options and announced new defaults so that TypeScript 7.0 could switch them on. If you skipped 6.0, these changes arrive all at once in 7.0:
strictis nowtrueby default.moduledefaults toesnext.targetdefaults to the latest stable ECMAScript version,es2025.typesdefaults to[], so TypeScript no longer loads every package innode_modules/@typesautomatically.rootDirdefaults to the folder that contains yourtsconfig.json.
To see what this means in practice, suppose you have a small Node.js project with the code in a src folder:
// src/index.ts
function greet(name) {
return `Hello, ${name}!`
}
console.log(greet("Ada"))
console.log(process.env.NODE_ENV)And a tsconfig.json that tells TypeScript to put the output in dist, which worked fine in earlier versions:
{
"compilerOptions": {
"outDir": "dist"
}
}When you run npx tsc with TypeScript 7.0, the build fails before it even checks your code:
tsconfig.json(1,24): error TS5011: The common source directory of 'tsconfig.json' is './src'. The 'rootDir' setting must be explicitly set to this or another path to adjust your output's file layout.Earlier versions worked out rootDir from your source files, so src/index.ts was compiled to dist/index.js. Now rootDir defaults to the project folder, and TypeScript asks you to set it so your output layout doesn't change silently. Set it, and run the build again:
{
"compilerOptions": {
"rootDir": "src",
"outDir": "dist"
}
}This time, TypeScript checks your code and reports two errors:
src/index.ts(1,16): error TS7006: Parameter 'name' implicitly has an 'any' type.
src/index.ts(6,13): error TS2591: Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig.The first error comes from strict mode, which is now on, so untyped parameters are no longer allowed. The second comes from the new types default: even if @types/node is installed, TypeScript doesn't load it until you list it.
To fix both, add a type to the parameter:
function greet(name: string) {
return `Hello, ${name}!`
}And add node to the types array:
{
"compilerOptions": {
"rootDir": "src",
"outDir": "dist",
"types": ["node"]
}
}Now npx tsc compiles the project into dist/index.js without errors. If you want the old behavior of loading every @types package, set "types": ["*"].
ES2025 types by default#
Because the default target is now es2025, the types for ES2025 features are available without any configuration. For example, you can use RegExp.escape() to safely build a regular expression from user input:
const userInput = "price (USD): $5.00?"
const pattern = new RegExp(RegExp.escape(userInput))
console.log(pattern.test("The price (USD): $5.00? is final")) // trueWithout RegExp.escape(), characters like (, $, and ? in the input would be treated as regex syntax.
Types for newer APIs, such as Temporal and the getOrInsert() method on Map, are available when you add "lib": ["esnext"] to your configuration. Keep in mind that types don't add runtime support. For example, Node.js 24 doesn't support Map.prototype.getOrInsert() yet, so the code compiles but fails when it runs.
Breaking changes and removed options#
The options TypeScript 6.0 deprecated are now removed. If your configuration still uses one of them, the build stops with an error like this:
tsconfig.json(1,79): error TS5102: Option 'baseUrl' has been removed. Please remove it from your configuration.
Use '"paths": {"*": ["./*"]}' instead.Here are the ones you're most likely to find in an older project:
| Option | What to do |
|---|---|
"target": "es5" | Use es2015 or later, and use a separate tool to compile down if you still support older browsers |
"downlevelIteration" | Remove it; it only applied to ES5 output |
"module": "amd", "umd", "system", or "none" | Use esnext, nodenext, preserve, or commonjs, and let a bundler produce other formats |
"moduleResolution": "node" (or node10) and "classic" | Use bundler if a bundler builds your app, or nodenext for Node.js |
"baseUrl" | Remove it and use paths with relative paths |
"outFile" | Use a bundler to produce a single file |
"esModuleInterop": false and "allowSyntheticDefaultImports": false | Remove them; both behaviors are always on now |
A few other changes can affect your code:
- Import assertions with
assertare no longer supported. Use import attributes withwithinstead, as inimport data from "./data.json" with { type: "json" }. - Declaring a namespace with the
modulekeyword, as inmodule Utils {}, is an error. Usenamespace Utils {}. - Running
tscwith file names when atsconfig.jsonexists in the folder is now an error:
error TS5112: tsconfig.json is present but will not be loaded if files are specified on commandline. Use '--ignoreConfig' to skip this error.If you meant to compile only that file, add the --ignoreConfig flag, as in npx tsc src/index.ts --ignoreConfig.
Tools that don't support TypeScript 7.0 yet#
TypeScript 7.0 ships without a JavaScript API. Tools that import the typescript package to work with the compiler, such as typescript-eslint, can't use TypeScript 7.0 yet. The TypeScript team plans to add a new API in TypeScript 7.1.
Until then, you can run both versions side by side. The TypeScript team publishes TypeScript 6.0 as @typescript/typescript6, and you can install it under the typescript name with an npm alias, so tools that import typescript keep getting TypeScript 6.0:
npm install -D "typescript@npm:@typescript/typescript6@^6.0.2" "@typescript/native@npm:typescript@^7.0.2"This adds these entries to your package.json:
{
"devDependencies": {
"@typescript/native": "npm:typescript@^7.0.2",
"typescript": "npm:@typescript/typescript6@^6.0.2"
}
}With this setup, npx tsc runs TypeScript 7.0, npx tsc6 runs TypeScript 6.0, and any tool that imports typescript gets TypeScript 6.0.
The same limitation affects editor tooling for frameworks that embed TypeScript in other files. At launch, the TypeScript team said Vue, Svelte, Astro, and MDX tooling, and Angular's template checking, will likely not be able to use TypeScript 7.0 yet. In those projects, you can still run tsc on TypeScript 7.0 for builds and CI, and keep TypeScript 6.0 for editor support.
How to upgrade to TypeScript 7.0#
The TypeScript team designed 6.0 as the stepping stone, so the smoothest path goes through it:
- Upgrade to TypeScript 6.0 and fix every deprecation warning it reports. The experimental ts5to6 tool can update some of these settings in your
tsconfig.jsonfor you. - Turn on
stableTypeOrderingin TypeScript 6.0 and fix any new errors. This option makes 6.0 order types the same way 7.0 does, which can change some error messages and declaration output. - Check that the tools you use with the TypeScript API, like linters and framework tooling, work with the side-by-side setup above.
- Upgrade to TypeScript 7.0 and run your full build and tests.
If your project already compiles on TypeScript 6.0 without ignoreDeprecations, the upgrade should mostly be a matter of installing the new version and enjoying faster builds.
Summary#
In this article, you learned what TypeScript 7.0 brings: a native compiler that's about 10x faster, parallel type-checking, a faster language server, new tsconfig.json defaults, and the removal of long-deprecated options. You also learned what to watch for when you upgrade, from the new rootDir and types defaults to tools that still need TypeScript 6.0.
The TypeScript team says it's now returning to new feature work, with releases every three to four months, starting with TypeScript 7.1 and its new API.
When your TypeScript app is ready to go live, you can deploy it with Sevalla's Application Hosting, which builds and runs it straight from your Git repository.