All tools

tsconfig.json Validator

Code

Parse a tsconfig.json file as JSONC and flag structural mistakes: unknown top-level keys, unknown compilerOptions keys, wrong value types, and malformed files/include/exclude/references/paths

Paste a tsconfig.json file and get back every structural mistake in it, checked against a curated list of the compilerOptions tsc actually recognizes. Comments and trailing commas are stripped before parsing, the same JSONC leniency tsc itself applies, so a file with a // note or a trailing comma won't falsely show as broken. It catches type mismatches like strict set to the string "true" instead of a real boolean, an enum option like target given a value outside its known set, and array-shaped fields like include given a plain string instead of a list. Unknown top-level keys and unrecognized compilerOptions are reported as warnings rather than errors, since tsc itself is often lenient about unfamiliar keys added by newer versions or tooling.

typescripttsconfigjsonvalidator

How to use tsconfig.json Validator

  • 1.Paste the contents of your tsconfig.json file into the input box.
  • 2.Review the issues list: errors mean a value's type or enum choice doesn't match what tsc expects, warnings are unrecognized keys that may still be valid in a newer TypeScript version.
  • 3.Check the compilerOptions and top-level key counts to confirm the file parsed the way you expected, especially after stripping comments.

Frequently asked questions

Does this actually run tsc to check my config?
No, it's a standalone parser and lookup against a curated list of common compilerOptions. It won't catch every edge case a real tsc invocation would, and a newer TypeScript release may add options this validator doesn't yet recognize.
Does it support JSONC comments and trailing commas?
Yes, // line comments, block comments, and trailing commas before a closing brace or bracket are stripped before parsing, matching how tsc reads tsconfig.json files in practice.
Why is an unknown compilerOption a warning instead of an error?
TypeScript adds new compilerOptions with each release, and this validator's known-options list won't always be current. Treating an unrecognized key as a hard error would produce false positives on a perfectly valid, newer config, so it's downgraded to a warning instead.
Does it resolve "extends" or check that referenced files actually exist?
No, it only checks that extends is a string or array of strings, not that the target file exists or that resolving it would produce a valid merged config. It works entirely on the text you paste, with no filesystem access.

Use via API, SDK, or MCP

cURL# Free: 1,000 req/day · Pro: 10,000 req/day
curl -X POST https://api.utilix.tech/v1/tools/tsconfig-validator \
  -H "Authorization: Bearer utx_live_..." \
  -H "Content-Type: application/json" \
  -d '{"text":"{\n  \"compilerOptions\": {\n    \"target\": \"ES2020\",\n    \"module\": \"ESNext\",\n    \"strict\": true\n  },\n  \"include\": [\"src/**/*.ts\"]\n}\n"}'

Get an API key from your dashboard · Full API docs →

Related tools

JSON → TypeScriptGenerate TypeScript interfaces from JSONJSONJSON Schema to TypeScriptConvert a JSON Schema document into TypeScript interfaces and typesJSONWeb App Manifest ValidatorValidate a web app manifest.json against the W3C Web App Manifest spec's installability requirements: name/short_name, start_url, display mode, and an icons array covering a 512x512 and a maskable iconNetwork