Using `resolveFullPaths` with watch mode cause the transpiled file not to have `.js` extenstion
See original GitHub issueAs title,
When using resolveFullPaths
in watch mode, the transpiled file doesnt have .js
extension
It work just fine without watch mode
tsconfig.json
{
"compilerOptions": {
....
},
"tsc-alias": {
"verbose": false,
"resolveFullPaths": true,
}
}
And run tsc -w & tsc-alias -w
causing the transpiled file lost its extension
Issue Analytics
- State:
- Created a year ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Compiled JavaScript import is missing file extension #40878
ts' , the compiler gives me error TS2691: An import path cannot end with a '.ts' extension. Consider importing './dep' instead . So...
Read more >How to transpile ES modules with webpack and Node.js
Learn how webpack interacts with and supports ES modules in this deep dive tutorial on transpilation in Node.js.
Read more >Typescript — How to solve the problem with unresolved path ...
js file containing the line with the path alias. The actual cause of the issue is that the tsc compiler does not transpiles...
Read more >TSConfig Reference - Docs on every TSConfig option
All relative paths found in the configuration file will be resolved ... extensions are included (e.g. .ts , .tsx , and .d.ts by...
Read more >Appending .js extension on relative import statements during ...
I usually just use the . js extension in import statements in typescript files as well and it works. Not using a file...
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
I have to mention this, actually solution number 1
concurrently \"tsc -w\" \"tsc-alias -w\"
, actually also not working if this is the first time you running this command ( meaning, there is no generated output yet )… On subsequent running of this command, it will work… Quick fix would betsc && (concurrently \"tsc -w\" \"tsc-alias -w\")
@tkcto I haven’t been able to reproduce this bug. That makes it exceedingly difficult to give a time estimate.