tsconfig-paths safe for production?
See original GitHub issueHi, is tsconfig-path
safe to use in production?
And what about perfomance impact of runtime module resolution?
Do you have any insight on these topics?
Thank you for solving this annoying absolute path resolution problem!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:8 (2 by maintainers)
Top Results From Across the Web
TSConfig Reference - Docs on every TSConfig option
All relative paths found in the configuration file will be resolved ... While you can use TypeScript to produce JavaScript code from TypeScript...
Read more >tsconfig-paths - npm Package Health Analysis - Snyk
The npm package tsconfig-paths was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as...
Read more >Why are these tsconfig paths not working? - Stack Overflow
I did a bit of digging and found that the tryPaths array produced by tsconfig-paths has absolute URLs relative to the project /cwd...
Read more >How to handle tsconfig path aliases : r/typescript - Reddit
Since VScode just loads the tsconfig files, it will all be fine and dandy in the IDE but then when running tests or...
Read more >Why TypeScript Paths Failed Me | Mitchell Simoens Blog
Oh good man why?! Yes, there is a fourth issue. When you are running code in development, TypeScript only loads a single tsconfig.json...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Any insights on how to use
tsconfig-paths
withtsc
when building the project?tsconfig-paths
works well with node andts-node
but not withtsc
For the record, I ran into the same issue and ended up using the tsc-alias package to replace the alias names with their relative path in the
outDir
folder.tsconfig.json
package.json