-
Notifications
You must be signed in to change notification settings - Fork 12.2k
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
Compile errors with 2.0.2 (worked with 2.0.0) #10633
Comments
I haven't had time to research the errors in my own typescript project, but I'm getting largely the same ones as you. Just wanted to throw it out there that I'm seeing very similar results. |
It really looks like you're compiling with some other tool; TypeScript does not produce errors that look like that. With it being unable to find lib.d.ts, it sounds like a problem with that tool not knowing how to resolve lib references correctly. What are you using to build with? |
I am using webpack. Most of the projects I am building use webpack via angular-cli. But one project uses webpack directly and it is still getting the errors above when using 2.0.2. Edit: I should probably note that I think angular-cli is using "awesome-typescript-loader" for webpack. And that is what my standalone project is using as well. |
I am also using webpack. |
Can you post a config file or something to help me bootstrap a repro? Odds are this is an issue with a webpack plugin but we'll need to track down the owner and let them know what to fix |
Sure, here is my webpack.config.dev.js:
My package.json looks like:
Note: this has the very specific Typescript version of 2.0.0, so the above should work. If it was changed to 2.0.2, the compile errors will then happen. I run the webpack through |
@s-panferov any ideas what is going on here? |
@RyanCavanaugh @s-panferov @mhegazy I also have this exact problem. I am running a webpack build for a project based on the Aurelia framework. A build that previously worked fine with no errors using typescript@v2.0.0 immediately started to fail with the same sort of errors, when I updated to typescript@v2.0.2. I am attaching my webpack config, typescript config, and package.json. This is definitely related to a change between v2.0.0 and v2.0.2. In my package.json I am specifying typescript v2.0.0, to have a working build, changing this to ^2.0.0, which will install v2.0.2, cause the build to fail. Don |
Would you be able to share the project? |
I provided the package.json, tsconfig, and webpack.config. Don |
not necessarily. i would like to have access to sample that reproduces the issue. helps us debug the problem. |
I had the same problem (and some related). I attach a minimal project which reproduces 3 of my problems. If you npm install && webpack there should be many errores. Most of them go away if I delete the lib compiler option. Still it won't find node typings and the custom typing I reference. Even after adding
It won't detect the typing.
|
2.0.2 is currently breaking us (see microsoft/TypeScript#10633)
The issue is wrong implementation of |
I'll take a look soon. |
The awesome-typescript-loader loader had a problem working with 2.0.2. That has since been fixed in a newer version. Have you tried that? |
Yes, it works now |
Thanks for reporting back. closing. |
TypeScript Version: 2.0.0 --> 2.0.2
Expected behavior: Code compiles!
Actual behavior: Code compiles when using 2.0.0. Code does not compile when using 2.0.2.
When specifying
"typescript": "2.0.0"
in my package.json, all my projects compile absolutely fine (as they have been doing for some time).However, when I upgrade (i.e. use either
"typescript": "^2.0.0"
or"typescript": "2.0.2"
) I get a lot of compile errors of the form:Not sure what else I can provide to help debug this, let me know and I'll get it.
Thanks.
The text was updated successfully, but these errors were encountered: