TypeScript's documentation is spread across six places, and each one stopped at a different version. Read the Handbook's type chapters. Check every tsconfig line you copy against the compiler you actually run. Take your TypeScript 7 facts from the dev blog, because that's where they're published first.
That's the whole map in four sentences, and the rest of this page is the evidence. I fetched more than fifty pages on October 23, 2026, read the parts I quote, and then ran the claims through TypeScript 5.9.3, 6.0.3 and 7.0.2 on Node 22.23.3. The script is in the Coding Dunia code-examples repo as typescript-documentation-map/, so you can rerun it. For the one-page definition of the language itself, see What Is TypeScript?. This page answers a different question: after you know what it is, where do you read?
Where Does TypeScript Documentation Live After Version 7?
TypeScript documentation lives in six places, and only one of them is the Handbook. The table lists each one and where it stood on October 23, 2026.
| Source | Good for | Where it stands |
|---|---|---|
| Handbook (typescriptlang.org/docs) | Learning the language | Release notes sidebar ends at TypeScript 6.0 |
| TSConfig reference | Looking up an option | Updated for 6.0 in places, still lists removed options |
| TypeScript dev blog | Release notes from 7.0 on | 7.0 on July 8, 7.1 beta on October 20 |
| Playground | Trying a snippet | Newest listed version is 6.0.3 |
| microsoft/TypeScript on GitHub | Source and tsc/CHANGES.md | The old typescript-go repo is archived |
| Node.js docs | Running .ts files | Type stripping is stable since v24.12.0 |
The Handbook's sidebar lists release notes for 6.0, 5.9, 5.8 and so on down to 1.1. There's no 7.0 entry, and typescript-7-0.html on the same path returns a 404. The docs home page sends "What's new in 7.0" and "What's upcoming in 7.1?" to the dev blog instead. So Handbook release notes are now an archive for 6.0 and older.
Don't use the "Last updated" stamp to judge a page. Every typescriptlang.org page I fetched that carries one, 53 of them, says Oct 23, 2026. That's the day I fetched them. It looks like a build date, not an edit date.
Where TypeScript 7 Itself Is Documented
Three pages cover 7.0 and none of them is in the Handbook. The 7.0 announcement covers the defaults, the removed options and the new --checkers, --builders and --singleThreaded flags. The 7.1 beta post covers what's next, including import attributes in ambient modules. And the CHANGES.md file the 7.0 post links to sits in microsoft/typescript-go, which GitHub marks as archived since September 1, 2026 with a README that says "This Repo Is Closed". A tsc/CHANGES.md now exists on the main branch of microsoft/TypeScript, so bookmark that one.
Which Handbook Pages Should You Read First?
Read the type-system chapters in this order, and read them before you touch the configuration pages:
- TypeScript in 5 Minutes. Inference, unions, generics and structural typing in one sitting.
- Everyday Types. Aliases against interfaces, literal types, and what
strictNullCheckschanges. - Narrowing. It covers
typeof, truthiness,in,instanceofand type predicates, which is the machinery behind most error messages. - Object Types, then Generics, then Creating Types from Types.
- Modules Theory, then Choosing Compiler Options, which is the only config guidance in the Handbook written in the
bundlerandnodenextera.
I'd read Narrowing before Generics. Most people go the other way, then stay puzzled by errors that the narrowing chapter explains head on.
Why trust these pages on TypeScript 7? The dev blog says practically any code that compiles cleanly on 6.0, with stableTypeOrdering on and no ignoreDeprecations set, "should compile identically" on 7.0. The one type-level change it calls out is that template literal inference now keeps a Unicode code point whole. The rest of its list is config defaults, removed options, a couple of syntax leftovers and how JavaScript files are analyzed. I also ran the three templates from Choosing Compiler Options, for a bundler, for Node.js and for a library. All three passed on 5.9.3, 6.0.3 and 7.0.2.
The Handbook's type-system chapters describe TypeScript 7 as accurately as they described 5.9, but its configuration pages still describe behavior that 7.0.2 rejects.
How Stale Is the TSConfig Reference?
About one option in ten is dead. How did I count? I copied the names of all 116 compilerOptions from the reference's quick navigation, wrote each into a tsconfig by itself, and ran 6.0.3 and 7.0.2 on every one.
- 104 options are accepted by both compilers.
- 3 were deprecated in 6.0 and removed in 7.0:
baseUrl,downlevelIterationandoutFile. - 9 were gone before 6.0, and the reference still documents them:
charset,importsNotUsedAsValues,keyofStringsOnly,noImplicitUseStrict,noStrictGenericChecks,out,preserveValueImports,suppressExcessPropertyErrorsandsuppressImplicitAnyIndexErrors. 6.0.3 answersTS5102, 7.0.2 calls them unknown options.
Some values fail even when the option survives. In my run target: es5, moduleResolution: node10 and classic, module: amd, umd, system and none, esModuleInterop: false, allowSyntheticDefaultImports: false and alwaysStrict: false all raised TS5107 on 6.0.3. On 7.0.2 they became TS5108, "has been removed". For module: none, 7.0.2 says the value isn't valid at all (TS6046). The reference still lists es5 and classic as allowed values.
Three Defaults the Docs Still Describe the Old Way
Defaults are where the docs mislead quietly, because nothing errors. You just get different output. I tested three sentences against all three compilers.
| Sentence in the docs | Where | 5.9.3 | 6.0.3 | 7.0.2 |
|---|---|---|---|---|
| "By default TypeScript targets ES5" | Handbook, The Basics | true | false | false |
rootDir defaults to the longest common path of the inputs | TSConfig reference | true | false | false |
Installed @types packages are "automatically included" | DefinitelyTyped README | true | TS2591 | TS2591 |
For the first row I compiled a template string with no tsconfig and looked for the ES5 .concat( rewrite. 5.9.3 emitted it, and the two newer compilers did not. For the second, a project with include: ["src"] and outDir: "dist" wrote dist/a.js on 5.9.3 and dist/src/a.js on 6.0.3 and 7.0.2. For the third, a file that reads process.version compiled on 5.9.3 with @types/node installed and failed with TS2591 on both newer versions. They need "types": ["node"].
The reference isn't wholly stale. Its types entry already says that below 6.0 every visible @types package is included and that the default is now [], which matches what I saw. Someone patched that entry and left the neighbors. The 7.0 announcement also says strict is on by default, and an untyped parameter with no strict setting failed with TS7006 on both 6.0.3 and 7.0.2 and passed on 5.9.3.
Handbook Tutorials That Fail on 7.0.2
Four tsconfig examples printed in the Handbook pass on 5.9.3 and fail on 7.0.2. I pasted each one as written.
The Gulp tutorial's target: "es5" is the typical failure. On 6.0.3 it prints "Option 'target=ES5' is deprecated and will stop functioning in TypeScript 7.0". On 7.0.2 the same line reads "Option 'target=ES5' has been removed". The Migrating from JavaScript tutorial uses the same target, the tsconfig.json page's include/exclude example uses module: system with outFile, and the Decorators page uses target: ES5. Don't copy any of them. The configs that survive are the ones from Choosing Compiler Options, the one Node's docs recommend, and the Node 24 base from the community tsconfig/bases repository.
Want a modern starting point without reading any of this? The tsconfig generator builds a config for TypeScript 7, and the readiness checker below reads yours and flags each removed option.
What Is Missing From the Docs Entirely?
Some TypeScript 7 behavior isn't in the Handbook or the reference at all. How do you find the gaps without reading every page twice? I compared tsc --help --all on both compilers. 7.0.2 prints eight flags that 6.0.3 doesn't: --checkers, --builders, --singleThreaded, --pprofDir, --quiet, --deduplicatePackages, --stableTypeOrdering and --watchInterval. I searched the saved text of the TSConfig reference and the tsc CLI Options page. Seven of the eight appear in neither. The exception is --stableTypeOrdering, which the CLI page lists with a default of false, while the 7.0 post says it's true by default and can't be turned off.
The 6.0 error text points at a setting the docs skip too. It tells you to specify "ignoreDeprecations": "6.0". That string appears on neither of the two pages, and --help --all doesn't list it. And the 7.0 post says outright that 7.0 ships without a programmatic API, with a different one expected in 7.1. Tools that import the compiler have to stay on a 6.0 API through the @typescript/typescript6 package. typescript-eslint is the usual victim. Its docs give a TypeScript range of >=4.8.4 <6.1.0 and never name version 7, so see the typescript-eslint peer range fix.
Which Pages Can You Skip?
Skip these, with the reason beside each. It's my judgment from what I opened, so disagree if your project differs.
- Gulp tutorial. Its tsconfig fails on 7.0.2, and a pipeline built on gulp and Browserify is not how most projects start now.
- ASP.NET Core tutorial. It says the quick start "requires Visual Studio 2015 or 2017". I didn't run it.
- The React page. It points to Create React App, Next.js and Gatsby. The React team deprecated Create React App on February 14, 2025. I didn't check Gatsby.
- Decorators. The page says it covers the experimental stage 2 version and that stage 3 decorators have existed since 5.0. Read it only for legacy
experimentalDecoratorscode. That option is still accepted on 7.0.2. - The Basics, one paragraph. The page is fine, but skip the line saying TypeScript targets ES5 by default.
- definitelytyped.org. The old site still shows a NuGet install route. The GitHub README is the live one, with the
typescaveat above. - The typescript-go repository. Archived.
- microsoft.github.io/TypeScript-New-Handbook/. It returned a 404 when I tried it.
What About Docs Outside typescriptlang.org?
Three outside sources earned a place. The Node.js docs say type stripping is stable since v24.12.0, ignores tsconfig.json, and recommend erasableSyntaxOnly and verbatimModuleSyntax. That config passed 5.9.3, 6.0.3 and 7.0.2 in my run. Our native TypeScript in Node.js guide covers the runtime side. The tsconfig/bases repository, which the tsconfig.json page recommends, has a node24.json that passed all three. And the DefinitelyTyped README is still the place to learn how @types versions work, including that it tests only TypeScript versions under two years old.
The Playground is the one to be careful with. I opened it on October 23 and the version button read v6.0.3. The list ran from 6.0.3 down through 5.9.3, with a Nightly entry above it. I didn't check what Nightly runs. Its target menu still offers ES3 and ES5, and its module menu still offers AMD, UMD and System. Run npx tsc locally before you believe a Playground result about 7.
Which Page Should You Open for What?
Match the job to the source, and verify the config part against the compiler you actually run.
| Your goal | Read | Then check against |
|---|---|---|
| Learn the language | 5 Minutes, Everyday Types, Narrowing | the TypeScript cheat sheet |
| Write a new tsconfig | Choosing Compiler Options | npx tsc --showConfig on 7.0.2 |
| Look up one option | TSConfig reference | npx tsc --help --all |
| Upgrade to TypeScript 7 | The 7.0 announcement | the TypeScript 7 migration guide and the 6 vs 7 differences |
| Run .ts files in Node | Node.js TypeScript docs | the strict mode guide for the checks Node skips |
If you only keep one habit from this page, keep this one. Treat a documentation page as a claim, not a fact, and let tsc settle it.
Check Your Own tsconfig.json
Paste it below for an instant readiness score against everything TypeScript 7 removed or changed. Runs in your browser, nothing is uploaded.
Need to check package.json too, or want the full breakdown? Use the full TypeScript 7 Migration Readiness Checker.