TSConfig Generator

How to use

1. 1Pick a preset that matches your project shape, for example Next.js (App Router), React + Vite, Node.js library, Node.js application, Browser library (ESM), Bun project, Deno-friendly ESM, Monorepo base, or Minimal strict. Each preset overwrites the options below.
2. 2Adjust target, module, moduleResolution, and jsx in the Target and modules card. ES2022 with ESNext + Bundler is the right modern default for projects built by Vite, Next.js, Webpack, or esbuild; NodeNext + NodeNext is the right pair for native Node ESM.
3. 3Tick the type libraries you need under Lib. Include DOM and DOM.Iterable for browser code, drop DOM for pure server code.
4. 4Tune the Type checking switches. Leave strict on for new code. The individual strict flags become read-only while strict is on, so the output stays a single line.
5. 5Set Emit options. Turn noEmit on for bundler-driven projects; turn it off and set outDir, rootDir, declaration, declarationMap, and sourceMap when tsc itself emits the JavaScript.
6. 6Add path aliases. baseUrl defaults to . when you add a path. Each alias maps to one or more comma-separated target locations. Include and exclude accept one glob per line.
7. 7Read the diagnostics under the output for any incompatible combinations, then click Copy or Download to save the file as tsconfig.json at the root of your project.

About this tool

TSConfig Generator builds a clean, copy-ready tsconfig.json from the choices people actually make on real TypeScript projects. Start with a preset for Next.js (App Router), React with Vite, a Node.js library, a Node.js application, a browser library that ships ESM, a Bun project, a Deno-friendly ESM setup, a monorepo base for extends, or a minimal strict baseline; every preset writes the modern, well-supported defaults instead of legacy ones (ES2022, ESNext, NodeNext, bundler resolution, isolatedModules). From there, every option is a single toggle: the strict master switch with the underlying noImplicitAny, strictNullChecks, strictFunctionTypes, strictBindCallApply, strictPropertyInitialization, noImplicitThis, alwaysStrict, and useUnknownInCatchVariables, plus the linting-style checks noUnusedLocals, noUnusedParameters, noFallthroughCasesInSwitch, noImplicitReturns, noUncheckedIndexedAccess, exactOptionalPropertyTypes, and noPropertyAccessFromIndexSignature. Module behavior is exposed through esModuleInterop, allowSyntheticDefaultImports, forceConsistentCasingInFileNames, resolveJsonModule, isolatedModules, verbatimModuleSyntax, allowImportingTsExtensions, and skipLibCheck. Emit settings cover noEmit, outDir, rootDir, declaration, declarationMap, sourceMap, removeComments, and emitDeclarationOnly with the right ones disabled automatically when noEmit is on. baseUrl and paths support multiple comma-separated targets, so you can model the @/utils style alias used in Next.js, the ~/components alias common in Nuxt or Vue, or a multi-target alias for a monorepo. The top-level extends, include, and exclude fields are editable. The output is rendered as a stable, minimal JSON file: defaults are dropped, the strict family collapses into a single line when strict is on, and you can optionally output JSONC with one-line inline comments documenting every emitted option. Choose 2 or 4 space indent, copy with one click, or download as tsconfig.json. A live diagnostics panel warns about incompatible combinations: CommonJS with bundler resolution, NodeNext module without NodeNext resolution, allowImportingTsExtensions without noEmit, declarationMap without declaration, emitDeclarationOnly without declaration, and paths without baseUrl. Useful for new repos, replacing the create-react-app or create-next-app default with something tighter, building a strict baseline for a library, standing up a monorepo workspace tsconfig that downstream packages extend, or settling a debate about which strict flags should be on. Everything runs locally in your browser. The chosen options are never uploaded.

Free to use. Works in your browser. No signup, no login.