search

antoine-coulon / skott

All-in-one devtool to automatically analyze, search and visualize project modules and dependencies from JavaScript, TypeScript (JSX/TSX) and Node.js (ES6, CommonJS)
MIT License
669 stars 25 forks source link

TypeScript path aliases are not resolved when the base tsconfig does not specify path aliases #32

Closed antoine-coulon closed 1 year ago

antoine-coulon commented 1 year ago

Thanks to @pigoz for reporting that issue!

The issue is related to TypeScript path alias resolution when having multiple tsconfig.json with some inheritance described as such:

tsconfig.json

{
  "extends": "./tsconfig.base.json"
}

tsconfig.base.json

{
  "compilerOptions": {
       "paths": {}
  }
}

In the case where tsconfig.json specifies some paths there is no problem merging all the paths found from both tsconfig and tsconfig.base.

However, it seems that when only the extended (in that example tsconfig.base.json) config file specifies "paths", Skott is not able to resolve any paths at all.