WebStorm 2017.1.1 is now available

We’re glad to announce that WebStorm 2017.1.1, the first bug-fix update for the recently released WebStorm 2017.1 is now available! It addresses the issues we found in the initial release and brings lots of great improvements.

A patch update should be available promptly for the users of WebStorm 2017.1, 2016.3.6 or 2016.3.5. If you’re using an earlier version, give WebStorm 2017.1 and its new features a try and download it from our website for a free 30-day evaluation.

Completion in webpack 2 configuration files

To help you migrate to webpack 2, WebStorm now provides code completion and documentation for options in the webpack.config.js file.


More flexibility with TypeScript imports

For some modules you might want to import their submodules instead of the entire module. For examples, for RxJS you might prefer to use import {Observable} from 'rxjs/Observable' instead of the more general import {Observable} from 'rxjs'.

To make WebStorm follow these rules when automatically adding imports, in Preferences | Editor | Code Style | TypeScript – Imports you can now specify the exact paths the IDE should avoid. Instead of them the IDE will look for alternative paths to import the same symbol.

If you are not happy with some specific import, hit Alt-Enter on it and select Change import… . You will see a list of other valid paths for this symbol.


Resolve roots in JavaScript projects

We added a bunch of improvements to the way WebStorm works when you want to resolve imports from several roots (for example, in a project that uses enhanced webpack module resolution) and have several project directories marked as Resource root for that.

Enable “Use paths relative the project, resource or sources roots” in Preferences | Editor | Code Style | JavaScript – Imports to make WebStorm use paths relative to this folder (or these folders) when generating imports.


In IntelliJ IDEA in JavaScript project make directories you want to resolve from as Sources roots.

Among other fixes and improvements:

  • Fixed false ESLint errors for the linebreak style (WEB-25487)
  • Support for data- attributes in JSX (WEB-22667)
  • Support for objects in Vue.js bindings (WEB-26092)
  • Performance improvements when working with TypeScript (WEB-25973)
  • Fixed the download of the TypeScript definitions files from the DefinitelyTyped repository in Preferences (WEB-26160)
  • Support for CSS Grid
  • Updated live templates for Angular

Please see the Release Notes for a full list of addressed issues.

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 Release Announcements and tagged , . Bookmark the permalink.

5 Responses to WebStorm 2017.1.1 is now available

  1. piotrd says:

    +1 for improvements in auto-importing JS modules! Now at least paths don’t start with ‘…/…/…’, but with ‘app/components/…’.

    One issue that is still left with that functionality: it still adds ‘/index’ to paths, e.g. import Button from 'app/components/layouts/Button/index', whereas I’d prefer the path to be 'app/components/layouts/Button' if there is no other file in directory that exports modules.

    Also, I noticed that by saying “In IntelliJ IDEA in JavaScript project make directories you want to resolve from as Sources roots.” you most probably meant “Resources”, right? There is no option to mark a dir as “Source root”, AFAICT.

  2. Mark McDermid says:

    The ctrl+cmd+space Mac emoji window now works in the editor! <3

  3. Velten says:

    Hmm, I cant get the scss file resolution to work with PhpStorm (17.3) to resolve “~app/…scss”. Accordingly to https://youtrack.jetbrains.com/issue/WEB-14019 its fixed. But the last commenter confirmed that it is not working. Could you clarify the state in the ticket? Thx,much

Leave a Reply to Ekaterina Prigara Cancel reply

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