TypeScript and ECMAScript 6 in ReSharper 9.1

13 Responses to TypeScript and ECMAScript 6 in ReSharper 9.1

1. 

   LordJZ says:

   April 21, 2015

   Tried 9.1, was disappointed at how bad it was at supporting ES 6 and TS 1.4. So, so many bugs and false positives.

   Even the destructuring stuff mentioned in this article is basically unusable:

   function f(a: number, b: string) { // 2 errors here
       return { a, b }
   }
   
   var a = f(10, "ss").a; // error

   • 

     Anton Lobov says:

     April 21, 2015

     Hi, LordJZ, thanks a lot for reporting. The thing you provided is a known issue, fix is on the way. It was not in the bugtracker, I created a ticket so that you’ll be able to follow it: https://youtrack.jetbrains.com/issue/RSRP-437988. By the way, it’s not a destructuring thing, it’s called short-hand object literal properties.

     Could you tell please about the others “So, so many bugs and false positives.” Are they different from the first problem, or do you have the same problem everywhere througout your code?
     Thanks!

     • 

       LordJZ says:

       April 21, 2015

       Here’s a test project I sent to you earlier with now 4 basic TS bugs: https://dl.dropboxusercontent.com/u/9241118/ReSharperTSFalsePositives.zip

       There are more, but it’s a start. Unfortunately, I feel that 9.1 RTM has more bugs than e.g. EAP 4 I loved so much.

       If some of these are fixed in your internal builds (waves?), is it possible to make these builds public (at least to license holders)? 9.1 is already bugged to death, I don’t mind having a few more but better TS support.

       • 

         Anton Lobov says:

         April 22, 2015

         Thanks a lot for reporting, two issues are fixed in what will be a bugfix update to 9.1, which will be released relatively soon.

         If there’s something else to report, feel free to use our bug tracker. 😉

       • 

         Anton Lobov says:

         April 30, 2015

         You’re welcome to try ReSharper 9.1.1 RC:
         https://confluence.jetbrains.com/display/ReSharper/ReSharper+9.1.1+EAP

         It should fix bugs reported by you. As to ‘implicit any’ checks, now you may go to ReSharper Settings -> Inspections Severity and disable them as a workaround, if they don’t work properly for you now.

   • 

     Jouda says:

     April 21, 2015

     Exactly, the whole ES6 and TS experience is really bad. The article conveniently does not mention many issues, most notable one being that it R# does not override VS internal error highlightings. That effectively means that it’s pretty unusable for anything ES6-related and will probably never work correctly in VS2013 (which won’t get ES6 support).

     • 

       Anton Lobov says:

       April 21, 2015

       Hi, Jouda. Do you have some issues not related to VS problems with ES6? If yes, please report them.

       Unfortunately, we cannot override JS highlightings provided by VS in any way, their API doesn’t provide such an option, and they don’t want to provide it. So, only VS2015 is a viable option for ES6 development. Hope they’ll fix remaining issues in their ES6 compatibility till the release.

     • 

       Anton Lobov says:

       April 21, 2015

       Sorry, I was wrong about VS not providing any means for disable error highlightings for JS. Here it is:
       http://i.imgur.com/RCdK7Od.png

       It’s VS2013, and it disables at least syntax errors.

       Will check out whether there exist some API for disabling syntax errors in VS2013-, so that ReSharper will do that by default if level is ES6+, at least.
       Thanks a lot.

     • 

       Anton Lobov says:

       April 22, 2015

       As we’ve found a workaround for VS own highlightings, hope that your issue is closed. If not, feel free to report other problems!

2. 

   Anton Lobov says:

   April 21, 2015

   So, a short notice for all users who experience problems with VS-provided highlightings for ES6 in JavaScript VS editor.

   You are able to disable them manually in VS options:
   http://i.imgur.com/RCdK7Od.png

   Sorry for not mentioning this in the article. And thanks to those who found this.

   • 

     Dmitry says:

     August 21, 2015

     Resharper seems to think values are never used if they are declared outside a class (in a module), and only used inside that class using EcmaScript 6. The variable a will show a warning that it not being used. Even if I turn that warning type off, the line will be grayed out.

     Here is an extremely simplified example:

     (function ($) {
     const a = “test”;

     class Cls {
     method() {
     console.log(a);
     }
     };

     return new Cls();
     });

     • 

       Anton Lobov says:

       August 21, 2015

       Thanks a lot for your report, Dmitry!
       I created an issue for it: https://youtrack.jetbrains.com/issue/RSRP-447321. Seems that block-scope types weren’t correctly added to control flow value analysis, will investigate and fix this. Unfortunately, this bug reproduces on 9.2 release, too.
       The only workaround now is to use “disable once with comment” for this issue type.

       • 

         Dmitry says:

         August 26, 2015

         This also the case for arrow functions.

         Thanks for the quick response.