Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
tsc-alias does not take custom tsconfig.json file
See original GitHub issueHi,
like above, I run command tsc-alias -p tsconfig.compile.json and I get error compilerOptions.paths is not set which is not tru for above file, but it is true for default tsconfig.json file. So I put paths to default tsconfig and the error changed to missing outDir which again, is missing from tsconfig.json but exists in tsconfig.compile.json.
This bug exists from @1.4.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
tsc - doesn't compile alias paths
TSC compiler alone can't resolve the alias paths. So in order to make it work you will be required to install additional dev...
Read more >Using the tsconfig file to configure the alias does not take ...
It is definitely bad to modify user's custom tsconfig.json without options! I found a workaround: Move current tsconfig.json to tsconfig.base.
Read more >tsc-alias
You can add aliases that reference other projects outside your tsconfig.json project by providing a relative path to the baseUrl.
Read more >How To Configure Path Aliases With TypeScript
The path is based on the location of my tsconfig.json file. For this example, I'll set baseUrl to the root of my project....
Read more >Typescript — How to solve the problem with unresolved ...
Setting up path aliases in the tsconfig.json file is really a nice ... The actual cause of the issue is that the tsc...
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 Free
Top 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
@Lazarencjusz @clifflaschet the issue of commander options being undefined has been fixed in pr #61. It will be fixed in the next release.
I observed the same issue in
1.4.0, when using a particular tsconfig file passed via the-poption. Not occurring in1.3.10.