When using the config extends functionnality, the ${configDir} in the paths is not resolved from the right location, it seems to pick the project root instead of the current package when using typescript 7.
Steps to reproduce
Here is a small repo to reproduce the issue configDir-resolving
Clone the repo, install dependencies and then run pnpm types-v6 which runs the type checking using typescript v6, it passes as expected, then run the pnpm types-v7 and it will fail.
You can then go in the file packages/sub-module/tsconfig.json and uncomment the paths config, which is the exact same as the one that should be extended, rerun the types-v7 command and now it passes.
Behavior with typescript@6.0
Path alias is properly resolved in the package from where the extended config is used.
Behavior with tsgo
Path alias is resolved to the project root instead of the package from where the extended config is used.
When using the config extends functionnality, the
${configDir}in the paths is not resolved from the right location, it seems to pick the project root instead of the current package when using typescript 7.Steps to reproduce
Here is a small repo to reproduce the issue configDir-resolving
Clone the repo, install dependencies and then run
pnpm types-v6which runs the type checking using typescript v6, it passes as expected, then run thepnpm types-v7and it will fail.You can then go in the file
packages/sub-module/tsconfig.jsonand uncomment the paths config, which is the exact same as the one that should be extended, rerun the types-v7 command and now it passes.Behavior with
typescript@6.0Path alias is properly resolved in the package from where the extended config is used.
Behavior with
tsgoPath alias is resolved to the project root instead of the package from where the extended config is used.