tsconfig.json Generator

The options this generator writes

The exact default output

Leave every control untouched and this is the file you get:

{
    "compilerOptions": {
        "target": "ES2022",
        "module": "ESNext",
        "moduleResolution": "node",
        "strict": true,
        "esModuleInterop": true,
        "skipLibCheck": true,
        "forceConsistentCasingInFileNames": true,
        "resolveJsonModule": true,
        "allowJs": false,
        "declaration": false,
        "sourceMap": false,
        "outDir": "./dist",
        "rootDir": "./src",
        "baseUrl": "."
    },
    "include": [
        "src/**/*"
    ],
    "exclude": [
        "node_modules",
        "dist"
    ]
}

Pick a jsx mode other than none and a "jsx" entry is appended to compilerOptions.

Strict mode: what it actually turns on

strict: true is an umbrella flag that enables the whole strict family, including noImplicitAny, strictNullChecks, strictFunctionTypes, strictBindCallApply, strictPropertyInitialization, noImplicitThis, useUnknownInCatchVariables and alwaysStrict. New projects should start with all of them on: retrofitting strictness later is painful.

Common mistakes

• Setting module: "CommonJS" for a Node ESM project. If your package.json says "type": "module", use NodeNext for both module and moduleResolution.
• Using tsc as a bundler. It is a compiler and type checker. Use Vite/esbuild/SWC for builds and tsc --noEmit for type checks.
• Compiling everything. Without an include list TypeScript picks up every .ts file it can see. The generated config always writes include: ["src/**/*"] and excludes node_modules and dist, so you are covered.
• Needing more than the config offers. This generator deliberately stays minimal. Options like lib, paths, isolatedModules or noEmit are easy to add by hand once the base file is in place.