-
Notifications
You must be signed in to change notification settings - Fork 202
ModuleResolution doesn't work correctly. #664
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
Comments
I should also note that changing the import to |
Which version of But last time we updated to TypeScript latest people's code broke so haven't done a quick push. Tracking it here though #663 🌹 |
PS: can you copy paste the code files here ... so I don't have to setup for testing :) |
My tsc version is 1.6.2. tsconfig.json:
main.ts:
test/index.ts:
|
I just tried typescript latest locally. Bug still exists. Reported here microsoft/TypeScript#5277 🌹 |
Thanks! |
…there. Closes TypeStrong/atom-typescript#664 closes microsoft/TypeScript#5277 feat(tsconfig) expand automatic compilation to lookup .tsx files (and also index for imports)
I have a project with a tsconfig.json that is compiled externally (and also does not generate d.ts files).
tsc will compile the project correctly, but atom will output lots of "module not found" errors when I use the node style module resolution. When I do add
compileOnSave: true
. It warns me that "the compile failed, but the emit succeeded".If it works for tsc, it should work for atom-typescript?
The text was updated successfully, but these errors were encountered: