WebStorm 2016.1 EAP, 145.596: bug fixes

The WebStorm team had a busy week after releasing WebStorm 2016.1 (if you missed the announcement, please follow this link). Today we’re making the EAP build for WebStorm 2016.1 bug-fix update available for download.

You can download it here, or if you’re subscribed to the EAP update channel, a patch-update from WebStorm 2016.1 should be available.

This EAP build brings various bug fixes and minor improvements that did not make it into the release build. Some noticeable fixes include: proper Less code highlighting, support for module augmentation pattern used in typing in TypeScript (WEB-20894), and injected JSX inside type="text/babel". Please find the full list of addressed issues in the Release notes.

Please report any issues you have with the IDE on our issue tracker. To get notifications of new EAP builds as they become available, subscribe to the EAP channel in Preferences | Appearance & Behavior | System Settings | Updates.

– JetBrains WebStorm Team

About Ekaterina Prigara

Ekaterina Prigara is WebStorm product marketing manager at JetBrains. She's passionate about new technologies, UX and coffee.
This entry was posted in Early Access Preview. Bookmark the permalink.

8 Responses to WebStorm 2016.1 EAP, 145.596: bug fixes

  1. Nikolay says:

    It is a little bit confusing to release 2016.1 EAP after 2016.1. Should not it be 2016.2 EAP?

    • Dennis Ushakov says:

      Sorry about confusion. That’s a bugfix update EAP, so it’s not 2016.2. We’ll try to come up with some better wording for that

  2. Prashant says:

    Have you thought using JDK style ‘uXX’ (update XX) for subsequent releases.
    Eg – Webstrom 2016.1u1, 2016.1u2, etc

  3. Elvis says:

    injected JSX inside type=”text/babel” – not work anyway.

    • Konstantin Ulitin says:

      Unfortunately, this fix (WEB-18276) didn’t get into the release, it is only fixed in builds with number >= 145.638, which are not publicly available yet. Sorry for the confusion.

  4. Terence Martin says:

    I find it kind of ironic that it’s 2016 and developers are still trying to work out version numbering schemes that aren’t confusing.

  5. Shawn Bigger says:

    We are experiencing allot of memory issues with 2016.1 on Mac.

    Prior to the upgrade we did not experience it as much, but we go from 2GB down to 100MB available memory after just a few debugging sessions.

    Wa any memory issues cleaned up in this EAP release? Any others experiencing this version hogging memory?

Leave a Reply

Your email address will not be published. Required fields are marked *