We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
typescript-transform-paths
Rather than tsconfig-paths, typescript-transform-paths seems much better. It's because the typescript-transform-paths changes the alias path import statements to be relative by transforming the TypeScript code in the compilation level. Beside, the tsconfig-paths runs on the runtime level like https://github.com/ilearnio/module-alias who never can avoid the module not found error in the TS-NODE
TS-NODE
Therefore, try to use the typescript-transform-paths and test some complicate projects who occurs the #20 error.
The text was updated successfully, but these errors were encountered:
7ee1809
samchon
No branches or pull requests
Rather than tsconfig-paths, typescript-transform-paths seems much better. It's because the typescript-transform-paths changes the alias path import statements to be relative by transforming the TypeScript code in the compilation level. Beside, the tsconfig-paths runs on the runtime level like https://github.com/ilearnio/module-alias who
never can avoid the module not found error in the
TS-NODE
Therefore, try to use the typescript-transform-paths and test some complicate projects who occurs the #20 error.
The text was updated successfully, but these errors were encountered: