typescript-v6

TypeScript 6 Skill

Build, configure, and debug TypeScript 6+ projects with precise compiler guidance and modern module/runtime patterns.

Before You Start

This skill is for real TypeScript 6+ project work: daily development, configuration, debugging, and upgrades.

Metric	Without Skill	With Skill
Upgrade Investigation Time	~90 min	~30 min
Common tsconfig Regressions	5+	0-1
Token Usage	High (manual diffing)	Low (release-note-grounded guidance)

Known Issues This Skill Prevents

1. Surprise build failures from missing types entries after upgrading
2. Unexpected dist/src/... output because rootDir was never explicit
3. Deprecated moduleResolution node or baseUrl settings surviving into a TS 6 migration
4. Confusion about when to use bundler vs nodenext
5. Overusing ignoreDeprecations: "6.0" as a long-term fix instead of a temporary migration aid
6. Misunderstanding --stableTypeOrdering as a production performance flag instead of a TS 6→7 comparison tool
7. Missing Node/test globals because TS 6+ projects often need explicit types entries
8. New side-effect import errors because TS 6 applies stricter side-effect import checking

Quick Start

Step 1: Make the important options explicit

{
  "compilerOptions": {
    "rootDir": "./src",
    "outDir": "./dist",
    "types": ["node"],
    "strict": true
  },
  "include": ["src/**/*"]
}

Why this matters: TypeScript 6 changed enough defaults and behaviors that explicit configuration now matters more in everyday work. rootDir and types are two of the most important settings to keep intentional.

Step 2: Pick module resolution deliberately

{
  "compilerOptions": {
    "module": "esnext",
    "moduleResolution": "bundler"
  }
}

Why this matters: TypeScript 6 deprecates moduleResolution: "node"/"node10". Bundled apps should usually choose bundler, while Node.js packages should usually choose nodenext.