Webstorm logo

The WebStorm Blog

The Smartest JavaScript IDE


WebStorm 2016.3.2 is now available

WebStorm 2016.3.2 is now available with many important bug fixes and improvements.

A patch-update is available for WebStorm 2016.3, 2016.3.1, as well as for the 2016.3.2 RC build. If you’re using an earlier version, now it’s a great time to give WebStorm 2016.3 and its new features a try and download it from our website for a free 30-day evaluation.

Among noticeable fixes and improvements:

  • The issue with using special symbols in Terminal with some keyboard layouts is now fixed
  • Support for debugging iOS apps with React Native 0.37+
  • Support for Stylelint 7.4+
  • Improvements in support for TypeScript 2.1

Improvements in support for async functions

We’ve added 2 new inspections that would help you working with the async functions. First one warns you if you forgot await when making an asynchronous function call:


Note that this inspection is enabled by default with “No highlighting, fix only” level, so no warning is shown in the editor. You can change that in Preferences | Editor | Inspections – Missing await for an async function call.

A quick-fix with Alt-Enter will add a missing await:


Another inspection will warn you if you haven’t handled the returned promise:


Extract method refactoring now has a special behavior for async functions – it would add async to the extracted function and await to the call:


Find a full list of addressed issues in the Release notes.

Your WebStorm Team

Comments below can no longer be edited.

15 Responses to WebStorm 2016.3.2 is now available

  1. aPoCoMiLogin says:

    December 13, 2016

    Docker integration for mac still not fixed :/

    Is there any eta for it? Since the issue is 9 months old..

    • Dmitry Filippov says:

      December 14, 2016

      We ran into some technical problems on Mac due to many changes in Docker itself. We’re aiming to bring the updated integration to 2017.1 versions of our tools, planned for next Spring. The fixes should be already available soon in our 2017.1 EAP builds. Keep an eye on this blog for the start of the EAP program to check the fixes before the official release.

      • aPoCoMiLogin says:

        December 19, 2016

        So if this will be in EAP I suppose it will be built-in not as is now, as plugin?

        • Ekaterina Prigara says:

          December 19, 2016

          It will be built-in in these early access preview builds.

  2. booya2nd says:

    December 14, 2016

    Appreciate the async inspections – thank you very much!

    Any chance the ‘find usage of /index.js’ will be tackled in the upcoming releases? Feels like it has never gotten any attention https://youtrack.jetbrains.com/issue/WEB-19752

    Keep up the good work!

    • Ekaterina Prigara says:

      December 14, 2016

      Thank you!
      We’ll have a closer look at that issue and hope we’ll fix it in the upcoming WebStorm 2017.1 release.

  3. Clay Shannon says:

    December 14, 2016

    Can WebStorm be used with “legacy” (old) ASP.NET projects (such as VB.NET projects that target .NET 3.5)?

    • Ekaterina Prigara says:

      December 14, 2016

      WebStorm doesn’t have support for ASP.NET. You might want to have a look at ReSharper.

  4. Rubén Canovaca Nieto says:

    December 15, 2016

    My WebStorm never update to this version… I click “Update and Restart”, but when software launch again, there is the same update popup again…

    Current version: 2016.3.1 (build 163.7443.51)
    New version: 2016.3.2 (build 169.9166.30)

    How can I fix it?

  5. Mörre Noseshine says:

    December 15, 2016

    At what point can still open bugs be considered forgotten and ignored? Because effectively that’s what’s happening.

    I can see good reasons for this, but I think it should be made an explicit process instead of relying on human qualities of forgetfulness and letting things slide (on both sides).

    How about on the one hand

    a) Requiring submitters to check if the bug still applies for a new (non-EAP) release, with an automated reminder to update their bug, or it will be closed e.g. as “no longer relevant”. I find this okay because some bug reports indeed do lose significance because I find other ways to do things.

    But this should be coupled with

    b) In turn Jetbrains promises to give updates on the status. Being told that ones bug is not high enough on the priority list to be worked on for the next release is better than the current state of “if we ignore it long enough they will probably forget”.

  6. Michiel Helvensteijn says:

    December 15, 2016

    I like that the async extract method refactoring is smart enough to distinguish between extracted code that contains `await` and extracted code that doesn’t.

    To improve this feature, however, I’d propose making “Extract asynchronous method” a separate refactoring instead (or adding a checkbox in the dialog). You may want to do an async/await extraction of code that doesn’t contain `await` yet, and the two types of extraction are semantically quite different.

    My need for this is not urgent enough to put in an official feature request. I just thought I’d mention the idea.

  7. Jack says:

    December 15, 2016

    Just updated to Webstorm 2016.3.2 today. Not sure if it is a coincidence but the page editor is now locking up after a few minutes. Basically the cursor freezes. I have restarted Webstorm and rebooted my computer (which is running OSX). basically makes the IDE unusable. Any thoughts or suggestions? Version information below:

    WebStorm 2016.3.2
    Build #WS-163.9166.30, built on December 12, 2016
    Licensed to Jack Johnston
    Subscription is active until February 28, 2017
    JRE: 1.8.0_112-release-408-b2 x86_64
    JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

    • Dennis Ushakov says:

      December 17, 2016

      Sorry to hear that, can you try creating an issue here with full contents of log folder (Help | Show log in …) attached

      • Jack says:

        December 17, 2016

        Ok will do. Thanks…