Buddy Code
Create account ↗
All tools
Free to use · No sign-up

TypeScript configuration provenance explorer

Trace effective TypeScript settings back through inherited configuration files, with source locations and override history.

Find where each TypeScript option came from. Choose a config folder, ZIP, or supplied text bundle, then select its entry config. Files stay in this browser; parent configs and package presets must be included.

TypeScript 5.9.3 · 100 JSON/JSONC files · 256 KB each / 2 MB combined · 32 inheritance levels · 30-second local deadline. Source code and plugins are never executed.

Paste a text bundle

JSON array of {"path":"tsconfig.json","text":"{…}"} entries. Paths are relative to the bundle root; preserve folders and include referenced package.json/config files. No source files are required.

4 files supplied. Folder and ZIP imports read JSON/JSONC only; source-file globs are shown without scanning project sources.

What it does

Trace effective TypeScript settings back through inherited configuration files, with source locations and override history.

How to use it

  1. Import a local configuration folder or ZIP with relative paths preserved, select the entry configuration, then inspect it.
  2. Follow extends chains and option origins. Missing parents remain explicit gaps; no preset packages are downloaded.
  3. The bundled TypeScript 5.9.3 compiler parses configuration locally. Source code, plugins and build commands are never executed.

Example

A project extends a shared base: target comes from the base, while strict is overridden in the project configuration.

Methodology

The pinned TypeScript 5.9.3 compiler parses a virtual filesystem containing only supplied files. A source trace records configuration inheritance and winning settings; paths retain their defining configuration origin.

Limitations

100 JSON/JSONC files, 256 KB per file / 2 MB combined, 5 MB ZIP, depth 32, 256 inheritance applications, two-million-character report and a 30-second worker deadline. Case-sensitive supplied filesystem only; missing parents or invalid settings make results partial. Only explicit compiler settings are listed; implied flags are not expanded. Files/include/exclude are selectors, not matched source files. No package installation, remote fetch, source compilation or plugin execution.

Automation

This tool runs in your browser. No upload API or MCP endpoint is available.

View capabilities and documentation

Reference updated

Join the conversation

Helpful tips, questions, and ideas for making this tool better.

Loading discussion…