Does tsconfig.json support comments?

The tsconfig.json format allows comments and trailing commas because it is parsed as JSONC. Many tools and libraries that read the file, however, expect strict JSON. This generator outputs plain JSON with no comments so the result works everywhere, including with a strict JSON.parse call.

What does moduleResolution actually control?

It controls the algorithm TypeScript uses to find imported files: "node" mimics Node.js CommonJS resolution, "bundler" matches how modern bundlers like Vite and esbuild resolve imports, and "node16" or "nodenext" follow Node.js native ESM rules including file extensions in imports.

Which target should I choose?

Pick the oldest JavaScript version your runtime needs to support. For current Node.js versions or evergreen browsers, ES2020 or newer is safe. Use ES5 only if you need to support very old browsers, since it disables newer syntax like optional chaining from being emitted natively.

Why enable esModuleInterop?

It lets you use default imports (e.g. import express from "express") for CommonJS packages that do not have a default export, which is how most npm packages are structured. Almost every modern project should keep this on.

Do I still need to install TypeScript separately?

Yes. This tool only generates the configuration file. Install the compiler with npm install -D typescript, save the generated JSON as tsconfig.json in your project root, then run npx tsc to type-check or build.

tsconfig Generator — Build a tsconfig.json for TypeScript…

Summary

Pick a preset or toggle target, module, strictness, and lib options to generate a ready-to-use tsconfig.json.

How it works

Choose a quick preset (Node.js, React + Vite, Next.js, npm Library) or start from Custom.
Set the target JavaScript version and module system for your build.
Pick a module resolution strategy and, if needed, a JSX mode.
Check which lib definitions to include, such as DOM or WebWorker.
Toggle strictness and interop flags like strict mode and esModuleInterop.
Set the output directory and root directory, then copy or download tsconfig.json.

Use cases

Bootstrapping a new TypeScript project without memorizing compiler option names.
Turning on strict type checking for an existing JavaScript codebase migrating to TypeScript.
Setting up a tsconfig.json for a React app built with Vite.
Preparing a tsconfig.json for a Next.js project with the correct JSX and module settings.
Generating a base config for an npm library that needs type declarations and source maps.
Checking which compiler options are recommended for a given module resolution strategy.

tsconfig Generator

Compiler Options