tsconfig.json patterns, diagnostics, and project references.
Compiler options that shape emitted JS and type-checking behavior.
{
"compilerOptions": {
"target": "ES2022",
"module": "ESNext",
"moduleResolution": "Bundler",
"strict": true,
"noEmit": true,
"skipLibCheck": true
}
}A `tsconfig.json` marks the project root and controls compilation behavior.
{
"compilerOptions": {
"target": "ES2022",
"module": "NodeNext",
"moduleResolution": "NodeNext",
"outDir": "dist",
"rootDir": "src",
"strict": true,
"esModuleInterop": true
},
"include": ["src/**/*"]
}NodeNext settings are common when using native ESM in Node.
{
"compilerOptions": {
"baseUrl": ".",
"paths": {
"@/*": ["src/*"]
}
}
}`paths` is useful for app code, but make sure your bundler or runtime understands the aliases too.
{
"compilerOptions": {
"strict": true
}
}The TSConfig reference documents `strict` as a top-level switch for stronger type checking.
{
"include": ["src/**/*.ts", "src/**/*.tsx"],
"exclude": ["dist", "node_modules"]
}File inclusion bugs are common, so keep these patterns simple and explicit.
Commands and flags that explain TypeScript behavior.
npx tsc --listFilesUseful when a file is unexpectedly missing or included.
npx tsc --extendedDiagnosticsHelpful in large projects when TypeScript builds feel slow.
npx tsc --showConfigUseful when debugging inherited configs and unexpected compiler options.
rm -rf dist *.tsbuildinfo && npx tsc --buildA clean rebuild can help when incremental caches get out of sync.
Split larger repos into buildable TypeScript projects.
{
"compilerOptions": {
"composite": true,
"declaration": true,
"outDir": "dist"
}
}Composite projects are required when you want to use `tsc --build` with references.
{
"references": [
{ "path": "../shared" }
]
}Project references help large monorepos build incrementally and in dependency order.
npx tsc --build --cleanUseful when resetting build-mode artifacts across a multi-project repo.