TypeScript Resolution Inspector
Paste a TypeScript traceResolution log to inspect an import, or add a second log to find the first recorded difference.
TypeScript Resolution Inspector
Paste a TypeScript traceResolution log to inspect an import, or add a second log to find the first recorded difference.
About TypeScript resolution traces
Follow the compiler’s evidence
The tool groups English traceResolution output by importing file and module specifier. A single log shows the recorded result and original lines. Adding B pairs matching imports and compares their recorded steps. If several B records match, choose one explicitly. Project-root mapping is optional and leaves the original evidence unchanged.
What a difference can tell you
A first recorded difference is a place to investigate, not proof of the cause. Unknown lines, truncated blocks and cached results can leave the evidence incomplete. The tool does not execute your project or reproduce Node or bundler resolution. English traces from TypeScript 6.0.3 have been tested; compatibility with other versions is not verified.
FAQ
Common questions and answers about this topic.
How do I obtain a traceResolution log?
Run tsc --traceResolution --locale en --pretty false in your project and save its output. Paste that text into A; B is optional. Each input accepts up to 5 MiB. The tool reads the logs locally in your browser.
Which TypeScript versions are verified?
English traceResolution output from TypeScript 6.0.3 has been tested. Other versions are not verified. Unrecognized lines remain available as original evidence and do not count as proof that two resolutions are equivalent.
Does a matching trace prove my app will run?
No. These are TypeScript compiler records, not runtime observations. Node and bundlers may resolve modules differently. Even the first recorded difference only identifies a point to investigate; it does not establish the root cause.