compilerOptions.paths not relative to ts config file on extends

[Chocobozzz]

Hi,

resolve-tspaths correctly handles tsconfig extends, but does not resolve compilerOptions.paths from tsconfig where it was defined. It means that paths are resolved from the main tsconfig file resulting in invalid path resolution.

[benyap]

Thanks for the issue @Chocobozzz. Could you provide a bit more detail, such as what the current behaviour is vs the expected behaviour?

[Chocobozzz]

Sure!

We have a tsconfig file defined in server/tools directory extending another one that is at the root of the repository. The parent tsconfig defines paths: https://github.com/Chocobozzz/PeerTube/blob/develop/tsconfig.json#L7. The server/tools tsconfig also defines paths because of this bug, but it should not.

resolve-tspaths correctly merge these tsconfig files, but then resolve paths property paths from server/tools. Since the paths property were defined in the root tsconfig, they should be resolved from the root of the repository.

[benyap]

I see, that makes sense. Will look into this and hopefully have a fix soon :)

[benyap]

@all-contributors add @Chocobozzz for bug report

[allcontributors]

@benyap

I've put up a pull request to add @Chocobozzz! 🎉