Why it matters
Path aliases such as @/components keep imports short, but baseUrl and paths are easy to misconfigure, and TypeScript, the bundler and the test runner each need to agree.
This resolver applies TypeScript's rules to your tsconfig so you can see exactly which file an alias should reach.
How to use it
- Type or paste your input; the example shows the format.
- Press Resolve. Results also update as you type.
- Read the summary line, then the table, notes or output below it.
- Copy or download what you need. Nothing leaves this page.
FAQ
Does Node understand tsconfig paths?
No. Node needs package.json imports (#alias) or a loader; bundlers need a plugin such as vite-tsconfig-paths.
Is my input uploaded?
No. The tool runs in your browser and nothing you type, paste or open is sent anywhere.
Can I rely on the result?
It follows the public specification or formula named on this page and says where it simplifies. Check anything critical against the official tool or documentation before you ship it.