Typescript 3.0 problems

Completed

I'm getting an error message 'no rule for Array, no lib.d.ts' when I updated my Visual Studio 2017 to the Typescript 3.0 sdk.  I'm having a lot of 'errors' in my code (highlighted red).  When disabling Typescript support, I don't have the errors highlighted.

 

I've got the latest EAP installed.

3
7 comments

Hello Jason!

 

Thank you for contacting us.

Could you please provide some sample solution demonstrating the issue? You can do it privately via 'Submit a request' form in the top of the page.

Thank you.

0
Avatar
Permanently deleted user

Same with me.

0

Hello!

 

Please try the latest ReSharper 2018.2 EAP build - https://www.jetbrains.com/resharper/eap/ and check if the problem is still reproduced.

Thank you.

0
Avatar
Permanently deleted user

Seems to have done the trick for me.

0
Avatar
Permanently deleted user

I have the same issue. I tried the link above for 2018.2 EAP build, but the problem persists.

The issue is on multiple computer with Windows 10, Visual Studio 2017 version 15.8.0, and TypeScript 3.0.

I have tried JetBrains.ReSharperUltimate.2017.3.5 versions and above with the same result.

I have cleared the Resharper cache via tools and manually, unloaded and reloaded the project, refreshed the TypeScript project, suspended/restarted Resharper, and most things listed on the following URLs:

https://stackoverflow.com/questions/48654852/resharper-cannot-resolve-symbol-when-the-code-well-compiled

https://stackoverflow.com/questions/15713167/resharper-can-not-resolve-symbol-even-when-project-builds

Nothing seems to work.

Regards...

 

1

Hello Warren!

 

Is there any chance you could share your solution with us? You can do it privately via 'Submit a request' form. We can also sign NDA if needed.

Thank you.

0
Avatar
Permanently deleted user

I think you may have misunderstood my previous post. I mentioned that I have the same issue caused by TypeScript 3.0 incompatibilities with all the versions of Resharper that I have tried.

What I have done to eliminate the thousands of false error messages that Resharper reports is to revert back to TypeScript 2.8 until Resharper is fully compatible with the new TypeScript version.

Regards...

0

Please sign in to leave a comment.