WebStorm 2016.2.4 is now available

Ekaterina Prigara

WebStorm 2016.2.4 is now available! You can download it from our website. A patch-update should be available, if you’re using WebStorm 2016.2.2 or 2016.2.3.

WebStorm 2016.2.4 addressed the issues with scrolling on macOS Sierra and brings over 30 bug-fixes. You can find a full list of addressed issues in the Release notes.

Your WebStorm Team

Comments below can no longer be edited.

10 Responses to WebStorm 2016.2.4 is now available

  1. Ihor says:

    October 19, 2016

    Is there a way to write plugins for WebStorm using JS/TS? Or probably you planning to make it possible?

    • Ekaterina Prigara says:

      October 20, 2016

      No, sorry, there’s no way to write them in any language other than Java or Kotlin since our platform.

  2. Nikolay Evseev says:

    October 20, 2016

    Chrome Debug Plugin stopped working after installing this update!

    Please do something urgently!!!

  3. Nikolay Evseev says:

    October 20, 2016

    Never mind my previous comment! It was an issue with a port!…..

    • Ekaterina Prigara says:

      October 20, 2016

      Good that it’s resolved now.

  4. Alfred Obialo says:

    October 30, 2016

    Will there be support for native script in Webstorm 2016.3 ?

  5. Gritsenko Maxim says:

    November 7, 2016

    After updating from 2016.2.3 to 2016.2.4 IDE fails to resolve inherited properties of all my classes in JS (ES6). So all properties that are declared in parent classes are marked as “unresolved”. The classes are declared as “class Foo extends Bar”, and have “@extends Bar” docs. Is there a special configuration hidden in new version, or is there a way to download the old version of IDE? (2016.2.3)

    • Ekaterina Prigara says:

      November 7, 2016

      Can you please send us a code sample or a screenshot. You can share a link to it here or report as a new issue on https://youtrack.jetbrains.com/issues/WEB
      Thank you!

      • Gritsenko Maxim says:

        November 29, 2016

        The latest update (2016.3.1) fixed this and some other issues. Thank you very much.