I.e. one shared base config where paths is defined and another that extends that base config to use in a specific project, tsconfig-paths does not properly recognize paths as defined. In order for it to recognize them, they need to be defined in the service/tsconfig.json, which does not align with how typescript does it. tsc will happily compile programs with the path mapping in the shared config, and it also outputs it when running tsc --showConfig in the service project, and incidentally, esbuild also happily resolves them as expected.
Given two
tsconfig.json
files as followsI.e. one shared base config where
paths
is defined and another that extends that base config to use in a specific project,tsconfig-paths
does not properly recognizepaths
as defined. In order for it to recognize them, they need to be defined in theservice/tsconfig.json
, which does not align with how typescript does it.tsc
will happily compile programs with the path mapping in the shared config, and it also outputs it when runningtsc --showConfig
in theservice
project, and incidentally,esbuild
also happily resolves them as expected.