Paste a tsconfig, keep JSONC comments and trailing commas, then review compilerOptions, strictness, module targets and preset drift before the config lands in code.
Choose a preset, edit the JSONC config and inspect diagnostics, preset differences and a recommended snippet.
Modern app baseline for Vite, Angular, webpack and similar bundler pipelines.
Clean for the curated rules
Skipping declaration checks can keep builds fast but may hide dependency type conflicts.
Keep it explicit and revisit it when debugging dependency type drift.compilerOptions.skipLibCheckstrict and noImplicitAny catch the most common hidden type-safety drift. The playground treats missing or disabled strictness as a review signal, not as a universal verdict.
Modern apps, Node services and packages need different moduleResolution choices. The evaluator flags legacy resolution and NodeNext mismatches before they become runtime surprises.
TypeScript paths do not configure bundlers, tests or Node by themselves. The page marks aliases as an integration note so reviewers know what else must be aligned.
tsconfig decisions connect to parsing, linting, formatting and schema contracts. These neighboring tools cover the next layer of the same review workflow.
No. The MVP is a browser-only JSONC validator and explainer. It does not read the filesystem, resolve extends or run the TypeScript compiler on a project graph.
Yes. The parser accepts common JSONC tsconfig syntax, including comments and trailing commas, then reports controlled parse diagnostics for invalid input.
An extended tsconfig can change compilerOptions, but this public page has no access to repository files. The info diagnostic keeps that boundary visible.
No. skipLibCheck is treated as a speed and maintenance tradeoff. The playground marks it as information so teams revisit it during dependency or declaration issues.