TS Config

It also covers the TS 6.0 deprecation cleanup ahead of 7.0: dropping moduleResolution node/node10, setting verbatimModuleSyntax, strict + noUncheckedIndexedAccess, explicit types, and explicit rootDir now that 6.0 no longer infers it.

Out of scope: TypeScript language syntax and idioms belong to ts-language-patterns; framework configs that ship their own tsconfig base (Next.js/Astro/Vite plugin skills) and non-TS build tooling are not covered.

TypeScript Config (TS 6.0)

Agent Workflow (MANDATORY)

Before writing any tsconfig, spawn 3 agents in parallel, one Agent call each with a name:

1. fuse-ai-pilot:explore-codebase - Detect runtime (Bun/Node/bundler), existing tsconfig, package.json type
2. fuse-ai-pilot:research-expert - Confirm current flags on typescriptlang.org release notes + runtime docs
3. mcp__context7__query-docs - /microsoft/typescript for any flag whose behavior is unclear

After writing, run fuse-ai-pilot:sniper for validation.

Overview

There are exactly two supported config trajectories in 2026. Pick by runtime, never mix.

Critical Rules

1. Never moduleResolution: node / node10 - deprecated in 6.0, removed in 7.0. Use bundler or nodenext.
2. Always verbatimModuleSyntax: true - both tracks. Forces explicit import type, matches Node's type stripping.
3. strict + noUncheckedIndexedAccess - strict is the 6.0 default; add noUncheckedIndexedAccess explicitly.
4. Set types explicitly - 6.0 defaults types to []. Add ["node"], ["bun"], etc. or you lose globals.
5. Set rootDir when sources are nested - 6.0 defaults rootDir to the tsconfig dir, no longer inferred.

Decision: which track?

Runs on Bun, or bundled by Vite/esbuild/webpack/Parcel?
  → Bundler track  → references/bundler-track.md

Runs directly on `node file.ts` (type stripping), or emits .js for Node?
  → Node track     → references/node-track.md

Migrating an existing 5.x config / seeing deprecation errors?
  → references/deprecations-6.md  (do this first, then pick a track)

Reference Guide

Concepts

Templates

Quick Reference

Bundler / Bun

{
  "compilerOptions": {
    "module": "Preserve",
    "moduleResolution": "bundler",
    "verbatimModuleSyntax": true,
    "allowImportingTsExtensions": true,
    "noEmit": true,
    "strict": true,
    "noUncheckedIndexedAccess": true
  }
}

Pure Node.js (native type stripping)

{
  "compilerOptions": {
    "module": "nodenext",
    "rewriteRelativeImportExtensions": true,
    "erasableSyntaxOnly": true,
    "verbatimModuleSyntax": true,
    "noEmit": true, // only if you never emit .js
    "strict": true
  }
}

Best Practices

DO

• Add "ignoreDeprecations": "6.0" temporarily while migrating, then remove it before adopting TS 7.0
• Use subpath imports "#/*": "./src/*" in package.json imports (supported under nodenext and bundler)
• Fold any baseUrl prefix into each paths entry (baseUrl is deprecated)

DON'T

• Mix module: Preserve with moduleResolution: nodenext (or vice-versa)
• Set esModuleInterop, allowSyntheticDefaultImports, or alwaysStrict to false (no longer allowed)
• Use enum, namespace with runtime code, or parameter properties in files run by Node's type stripping