-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
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
tsc-alias incorrectly adds .js extension to a module from node_modules #197
Comments
Fixed with this: {
"compilerOptions": {
// ...
},
"tsc-alias": {
"debug": true,
"verbose": true,
"replacers": {
"base-url": {
"enabled": false
}
}
}
} |
Reopening because that configuration broke some other stuff. I believe this is a bug. if the module specifier is not a file path, tsc-alias shouldn't add a |
Ended up writing this: https://github.com/olalonde/tsc-module-loader |
Was this by any chance where you had a file with the same name as something you were importing? In my case I had a file called react.ts of react tools with used |
Having the exact bug. |
It's not only that, there should also be an option for specifying the file extensions in the transpiled files, especially when you consider The whole JS/CJS/ESM/node ecosystem is a mess TBH. It seems like an eternal process of trying to glue all the bits together. |
…e same module name exists (justkey007#197)
I have a file
stripe.ts
which imports thestripe
module (npm install stripe). tsc-alias adds a .js extension to it for some reason.becomes
The text was updated successfully, but these errors were encountered: