TSConfig Compatibility Checker
Paste tsconfig.json and optional package.json to find TypeScript module/moduleResolution mismatches, JSX/lib gaps, package type conflicts and publish-mode issues.
When to use TSConfig Matrix
Use this when TypeScript settings work in one environment but fail in Node, a bundler, test runner or package publish flow. The matrix explains the compatibility conflict instead of treating settings in isolation.
TSConfig Compatibility Checker - moduleResolution NodeNext and Bundler Matrix
TSConfig problems often come from combinations: module with moduleResolution, JSX with lib, package type with output format, path aliases with runtime support and import extension settings with emit mode. Reading each option separately rarely explains the failure.
TSConfig Matrix accepts the config directly and produces a compatibility table for common modes such as Node library, browser app and package publishing. The goal is a faster first answer before changing presets across a monorepo.
The checker uses deterministic heuristics and should be confirmed with your real TypeScript version, bundler and test runner. It is most useful for review, migration planning and narrowing which setting deserves the next experiment.
- Runs in the browser for fast first-pass analysis.
- Does not require login, upload, server storage or build access.
- Works best with redacted snippets copied from DevTools, config files, framework examples or issue reports.
- Findings are practical review signals and should be confirmed with the official toolchain before production changes.
TSConfig problems often come from combinations: module with moduleResolution, JSX with lib, package type with output format, path aliases with runtime support and import extension settings with emit mode. Reading each option separately rarely explains the failure.
TSConfig Matrix accepts the config directly and produces a compatibility table for common modes such as Node library, browser app and package publishing. The goal is a faster first answer before changing presets across a monorepo.
The checker uses deterministic heuristics and should be confirmed with your real TypeScript version, bundler and test runner. It is most useful for review, migration planning and narrowing which setting deserves the next experiment.