Feature: supporting tsconfig.json "paths" mapping about ts-tools

[printjs]

Yes,I always use ts-node and tsconfig-paths.This combination works very well.Expecting to become a built-in.Your project is very good.I like it.

[printjs]

@AviVahl

[printjs]

#1

[AviVahl]

Thanks for the report. First one! :)

If you also register https://www.npmjs.com/package/tsconfig-paths

Does it work?

[AviVahl]

I'll also think about built-in support without the additional overhead...

[AviVahl]

Just to clarify the current status:

node-typescript-support does not apply any additional processing of the sources (other than transpilation), and thus generated code that relies on mapped "paths" will fail at runtime.

It should be noted that type checking still works (or supposed to work) and report proper type errors, even for types coming out of mapped locations. The generated JS code does not have the paths mapped and fails on Node when running it as-is.

Using node-typescript-support with tsconfig.paths should be possible as well (like using that project with ts-node. You would need to register both.

Built-in support for paths is being considered. If tsconfig.paths works for now, it is on a lower priority than other features or refactors.

[AviVahl]

Fixed in master and will be fixed in the upcoming release of @ts-tools/node.

[AviVahl]

@printjs baseUrl and paths are now supported in @ts-tools/[email protected]. No need for additional external packages.