Early Access Program

WebStorm 2019.3 EAP #4: Improvements in Debugger, Push Any Branch

WebStorm 2019.3 Early Preview build #4 is now available!

If you’re unfamiliar with our Early Access Program or if you want to catch up on all the new features, check out the previous EAP blog posts.

The Toolbox App is the easiest way to get the EAP builds and keep both your stable WebStorm version and any EAP versions up to date. Or you can download the EAP builds from our website. You can also get notified right from the IDE when a new EAP build is available: go to Preferences | Appearance & Behavior | System Settings | Updates and select “Automatically check updates for Early Access Program”.


Important! WebStorm EAP builds are not fully tested and might be unstable.

Here are some of the highlights of WebStorm 2019.3 EAP #4 (build 193.4099.10). For the full list of issues fixed in this update, see the Release Notes.

See return values in Variables view

We’ve added a new Show Method Return Values option to the debugger (you need to click the gear icon on the debugger’s left panel to enable it). This option allows you to see what value the method returns without using console.log, creating an extra variable or using Evaluate expression.

With this option on, you’ll see the return value right on top of the variables view as soon as you step through this line of code (pause on it first and then click Step over or Step into). You can change its value if needed.

Show method return values in debugger

Enable Show Method Return Values in debugger tool window

Improved memory usage when debugging with source maps

In the past weeks we’ve been working a lot on improving the IDE memory usage when debugging the code with source maps. The debugger now uses soft references when working with source maps which means that the memory can be easily freed when the memory limit is reached.

If you have a memory indication on in the IDE status bar (Preferences/Settings | Appearance & Behavior | Appearance – Show memory indicator), click it to free the soft-referenced memory.

Better detection of TODOs in JSX code

We’ve fixed a bunch of issues related to the todo comments in JSX code. For example, now WebStorm sees todo comments in multiline JavaScript blocks inside JSX tags and works with these comments better in Flow files.

Todo-comments in JSX

Push any branch

You can now push changes from any branch right from the Branches popup – select a branch and then use the Push action in the menu.

Push changes from any branch

Previously, you could only push changes from the branch you’re currently working with. That meant that you had to switch to the branch first and only after that you could push the changes.

Please report any issues on our issue tracker, and stay tuned for the next week’s update!

The WebStorm Team

Comments below can no longer be edited.

10 Responses to WebStorm 2019.3 EAP #4: Improvements in Debugger, Push Any Branch

  1. Avatar

    cinan says:

    October 4, 2019

    Push any branch – yay!

  2. Avatar

    Shahnawaz Khan says:

    October 5, 2019

    Wow now i can easily push my data in GitHub and in other branches too… thanks jetbrains for implementing this new feature… keep it up! 🙂

  3. Avatar

    Luiz Antonio Batista da Silva says:

    October 16, 2019

    Sorry to ask again, but intellisense is broken when it comes to Node 12 ‘createRequire’ feature and we are working blind here with no intellisense at all on our code as we cannot drop the use of createRequire.

    Could you please consider to put WEB-40776 on the roadmap for this final release?

    Thank you!

    • Ekaterina Prigara

      Ekaterina Prigara says:

      October 16, 2019

      Sorry, this is a big change and we have already reached a feature freeze stage for the upcoming WebStorm 2019.3 release. We see what we can do or if there a workaround available, but unfortunately we can’t promise that it will be implemented in WebStorm 2019.3.

      • Avatar

        Luiz Antonio Batista da Silva says:

        October 16, 2019

        Thank you.

  4. Avatar

    soywiz says:

    November 15, 2019

    Latest EAP versions including this one in all the intelliJ-based products (including WS and Ultimate) have issues with the caret in input dialogs on non-retina resolutions/displays. Easily reproducible with RDM (https://github.com/avibrazil/RDM). I have a retina display, but reduce the resolution to get better overall performance.
    When you start typing, the caret “|” moves more to the right than expected “hello |”, “hello world |” and so on. Probably a wrong division or multiplication with the pixel ratio somewhere.
    Early EAP versions didn’t have this issue, but the latest ones have this, so maybe something introduced in the past month/two months as much?

    • Ekaterina Ryabukha

      Ekaterina Ryabukha says:

      November 15, 2019

      Hello, Carlos! As per this issue, the JDK build with the fix hasn’t been published yet. Please stay tuned for the upcoming announcements.

  5. Avatar

    John Fazzie says:

    January 27, 2020

    The debugger variable resolving speed seems to have slowed down tremendously with this release. Previously, all variables would be resolved almost instantaneously. Now, the debugger slowly steps through each variable resolving them. Can you look into this?