Early Access Program

WebStorm 2016.2 EAP, 162.844: convert to arrow function, custom background

Fresh WebStorm 2016.2 EAP build (162.844) is now ready! You can download it here or, if you have installed the previous WebStorm 2016.2 EAP build (162.646), you should soon get a notification in the IDE about a patch update.

Convert to arrow function

We’re now working on a set of intentions that will help you to convert your code to ES6. In WebStorm 2016.1 we’ve introduced Convert to ES6 template string action. And the new intention that is now available is for converting to arrow functions.

For example, you can convert a  callback function to arrow function by hitting Alt-Enter on the function keyword:


You can also convert arrow function to a shorthand arrow function:


We’d be very happy to hear your feedback on that! In the next WebStorm 2016.2 EAP builds we’re planning to highlight the code which can be converted and allow bulk fixes across the project files.

Improvements in Git support

First, the VSC log (in Git and also Mercurial) now updates in the background immediately after every change (e.g. commit, fetch, rebase, etc) –  now it should be fully loaded right when you open it, you don’t have to wait for it to update. Moreover, the progress bar has also been improved.

Second, WebStorm 2016.2 fixes the issue the with the case-only renames in Git for Windows and OS X.

Custom background

Last but not least, you can now set a background image for the IDE. Hit Shift-Cmd-A to invoke the Find action dialog and search for Set Background Image. You’ll be offered to select the image file, set the opacity of the image and preview the result.

The full list of issues is available in the Release notes.

Read about the features and improvements added in previous WebStorm 2016.2 EAP builds:

  • WebStorm 2016.2 EAP, 162.646: Integration with Angular CLI and new Angular 2 live templates. Support for fonts with ligatures. Debugging in Firefox 36+. Option to run build tasks before Run and Debug.
  • WebStorm 2016.2 EAP, 162.232: Working with patches in VCS is now easier. Drag images, JavaScript or CSS files into an HTML file in the editor to generate src, script or link tags for them. New .let and .const postfix templates have been added.
  • WebStorm 2016.2 EAP, 162.74: Improved React support (coding assistance for props, auto imports for components in TSX, and more), smarter support for enums in TypeScript, and improved Dart support.

Please share your feedback and report any issues to 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.

Your WebStorm Team

Comments below can no longer be edited.

13 Responses to WebStorm 2016.2 EAP, 162.844: convert to arrow function, custom background

  1. Avatar

    Jérôme Beau says:

    June 9, 2016

    Too bad that the Set background feature does not provide a visual preview the file you select. That’s pretty unusable without this.

  2. Avatar

    hegfirose says:

    June 22, 2016

    WebStorm 2016.2 EAP
    Build #WS-162.917.18, built on June 15, 2016

    node_modules folder is hidden automatically. Is this is a bug or a new feature?

    • Ekaterina Prigara

      Ekaterina Prigara says:

      June 22, 2016

      Can you please elaborate what do you mean by hidden? Thank you!

      • Avatar

        hegfirose says:

        June 23, 2016

        See the screenshot http://imgur.com/DdoOCvu.

        There is a folder named `node_modules` under [example] dir (as terminal ls), but it is not visible on the ‘Project’ tab.

        WebStorm 2016.2 EAP
        Build #WS-162.1024.2, built on June 21, 2016
        WebStorm EAP User
        Expiration date: July 21, 2016
        JRE: 1.8.0_45-b14 x86_64
        JVM: Java HotSpot(TM) 64-Bit Server VM by Oracle Corporation

        • Ekaterina Prigara

          Ekaterina Prigara says:

          June 23, 2016

          It seems that the issue might be related with .ignore plugin. Do you have this issue with node_modules in all your projects? Can you please try to temporarily disable the plugin and see if the problem remains. We’ll also investigate that on our side. Thank you!

  3. Avatar

    Tyler Garlick says:

    June 29, 2016

    I still would like to see Options > Languages & Frameworks > JavaScript > LIbraries dialog be a multi-select so I can download more than one framework at a time.

    • Ekaterina Prigara

      Ekaterina Prigara says:

      June 29, 2016

      Thank you for your feedback. We hope to rework this functionality now when all the d.ts files became available via npm.

  4. Avatar

    Michael Hasenstein says:

    July 7, 2016

    There have not been any other blog posts for several newer EAPs but I would like to ask something.

    Of the many bugs I filed that are still open – and I occasionally go through all of them, testing against the latest EAP – the ones that really bug me are about autocompletion results. It often is useless right now, actually more so than in the past. I have nearly 100% JSDoc for everything so it should actually be easier. I get to see a lot of garbage suggestions, and most disturbingly, a lot of them are from places that are actually quite impossible. For example, I get suggestions for properties that only exist somewhere in some file under ./test/ in an object used inside a function only, it’s never even handed around. I even got suggestions from .eslintrc.js. The issue that I get a hundred suggestions on `module.exports.<>` seems part of the overall problem – it just picks up anything declared anywhere, with no regard for scope. This is a frequent issue, I often find properties that appear deep inside some node_modules/ files _purely internal internal objects_! They just have the same name. For example, there is a “var data = {…};” in some internal function somewhere – chances are I get to see the properties defined there in my own “data” property, just because it happens to have the same name and also be an object.

    Of course it often works, but it seems whenever I actually need it it doesn’t.


    WEB-17110 Autocompletion results are wrong

    WEB-19318 Autocompletion shows keys on module.exports that are not there (they are in other modules)

    WEB-20434 node.js: WS assumes variables in npm packages are available everywhere in normal code

    WEB-21968 Type detection picking up suggestions from completely and obviously impossible places – even from local variables in other files inside functions

    I see this kind of stuff _all the time_ now, and in many cases it would be much better if WS would not even attempt to infer anything from the code (given the lack of quality in the results) but just straight use the JSDoc info I provide everywhere.

    Maybe that’s an easy quick fix: A configurable option to restrict the attempts of WS to auto-detect types. I already have “Only type-based completion” enabled in Settings => Languages & Frameworks => Javascript