WebStorm 11.0.2 is now available

WebStorm 11.0.2 is now available! You can download it from our website or install a new version directly from WebStorm 11.0.1.
This update brings lots of bug fixes and various improvements. Here are some highlights.

Better support for npm 3

npm 3 brings a new flat structure of dependencies. Previously, to make indexing faster WebStorm indexed only top level folders in the node_modules directory, excluding module’s own dependencies. With the new flat structure the old approach doesn’t work. So in WebStorm 11.0.2 we now first check the list of the dependencies in the package.json file and then index only those modules.


Improved auto import for any TypeScript symbol

WebStorm can now automatically import any TypeScript symbol from other project files and modules right as you type.


We have also updated our built-in TypeScript compiler to version 1.7.3 and improved support for multiple tsconfig.json files in one project.

Redesigned Dart Problems view

For Dart projects WebStorm 11.0.2 brings an improved Problems window. By default it shows the summary of all issues identified in the project by the Dart Analysis Server. Use filters (click Filter icon on the left pane of the tool window) to limit the scope to the current package or file.


A simple double-click on the issue will take you to its location. Start typing the file name or some symbols from the error message to quickly search in the list of issues. Note that all these issues are also automatically highlighted right in the editor as you type.

Support for the bind operator ES7 proposal

WebStorm now supports the proposed ES7 syntax for the bind operator. Please note that it’s a proposed language feature, so its syntax, the support in compilers and in WebStorm might change in the future.


New WebStorm logo

After updating WebStorm you will notice a number of visual changes in the product, such as a new logo and splash screen and on the product website. We are very excited to present you the new JetBrains branding! You can find more details about that in this blog post.

The full list of issues fixed in WebStorm 11.0.2 is available in the release notes (please also see the release notes for WebStorm 11.0.2 EAP and 11.0.2 RC).
Please report any problems in our issue tracker. Thanks!

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

47 Responses to WebStorm 11.0.2 is now available

  1. I have 11.0.1 version but if I click Check for Updates I get the message that says that I have the latest version!
    Any ideas?

  2. Jim says:

    Your website is also broke. Download is for version 10.0.4, not 11.0.2.

  3. I’ll also file a bug – but what happened between the last EAP for 11.0.2 and this release? All of a sudden node.js (5.2.0) module methods are unknown to inspections and auto-completions and cause “Unresolved function or method” errors! That wasn’t the case before I upgraded from 143.1183.13, the last EAP before this release. I tried “Invalidate cache and restart”. Of course I made sure “Node.js core library is enabled.” and scopes are still okay too. That’s a major bug!

  4. Travis Odom says:

    Is the IDE able to apply this update as an automatic patch? I’ve tried the 10.0 fix of just repeatedly telling it ‘Check for Updates,’ but that doesn’t seem to be working.

    • Ekaterina Prigara says:

      Sorry, we don’t provide patches for updates from one major version to another. And unfortunately for this update we don’t offer a patch from 11.0.1 as well. Sorry for the inconvenience.

      • Chris Case says:

        Is there a reason a patch isn’t provided for 11.0.1 to 11.0.2? It’s very inconvenient to download a new version (especially on linux).

        • Terence Martin says:

          Actually I find this to be less of an issue under Linux, where I just extract the tarball to my /home/tmartin/local directory and then modify the shell script that I use to launch it (I keep the older versions around to combat bugs in newer versions).

          Where this is mind bogglingly annoying is under windows, where it first has to uninstall the old version before installing the new one, so all of my pinned shortcuts go away or stop working.

        • Dan says:

          It’s ridiculously inconvenient and is troubling when this is simply an increment of the PATCH version number.

          From time to time, RubyMine and IntelliJ suffer the exact same full-download for PATCH version level upgrade.

          From a perception perspective, understand that this has many of us questioning how safe PATCH version upgrades are. Food for thought.

  5. Adam Seldon says:

    Find the JetBrains IDEs excellent. And the install / upgrade process is alot easier than say installiing a new version of Apple’s Xcode which is shockingly painful. The recent Xcode 7.2 release took hours to download (4.7 GB), install, then update with new documentation and simulators, and finally re-install Plugins requiring new UUIDs applied to info.plist files etc. However, having to re-install the entire Webstorm IDE for a patch release (using the Semver jargon) is far from ideal… but thankfully no plugin re-installs were required.

  6. I chose silently unninstal older version. My settings and configuration was lost yet. Typescript compiller stopped works correctly => throw that i haven´t tsconfig.json in my project.

    If I knew what await me I never would have clicked on the update button.

  7. Jerzy M says:

    I’ve updated to version 11.0.2 from 11.0.1 without problem, but I’ve to back to 11.0.1 becouse TypeScript – tsconfig.json support is broken, somehow it can’t find main file of my component implementation. tsconfig is stored in folder with all .ts files, component is divided to multiple files.

    “compilerOptions”: {
    “target”: “es5”,
    “module”: “commonjs”,
    “noImplicitAny”: true,
    “removeComments”: true,
    “preserveConstEnums”: true,
    “out”: “./dir/component.js”,
    “sourceMap”: true

  8. John O'Byrne says:

    the 64bit version does not start for me (32 bit version works though)

    Internal error. Please report to http://jb.gg/ide/critical-startup-errors

    java.lang.IllegalArgumentException: Argument for @NotNull parameter ‘componentManager’ of com/intellij/openapi/components/ServiceManager.doGetService must not be null
    at com.intellij.openapi.components.ServiceManager.doGetService(ServiceManager.java)
    at com.intellij.openapi.components.ServiceManager.getService(ServiceManager.java:37)
    at com.intellij.openapi.application.ApplicationInfo.getInstance(ApplicationInfo.java:49)
    at com.intellij.openapi.application.ex.ApplicationInfoEx.getInstanceEx(ApplicationInfoEx.java:31)
    at com.intellij.ui.Splash.showLicenseeInfo(Splash.java:183)
    at com.intellij.ui.Splash$SplashImage.paintIcon(Splash.java:225)
    at javax.swing.plaf.basic.BasicLabelUI.paint(BasicLabelUI.java:150)
    at javax.swing.plaf.ComponentUI.update(ComponentUI.java:143)
    at javax.swing.JComponent.paintComponent(JComponent.java:760)
    at com.intellij.ui.Splash$1.paintComponent(Splash.java:76)
    at javax.swing.JComponent.paint(JComponent.java:1037)
    at javax.swing.JComponent.paintChildren(JComponent.java:870)
    at javax.swing.JComponent.paint(JComponent.java:1046)
    at javax.swing.JComponent.paintChildren(JComponent.java:870)
    at javax.swing.JComponent.paint(JComponent.java:1046)
    at javax.swing.JLayeredPane.paint(JLayeredPane.java:567)
    at javax.swing.JComponent.paintChildren(JComponent.java:870)
    at javax.swing.JComponent.paintToOffscreen(JComponent.java:5139)
    at javax.swing.RepaintManager$PaintManager.paintDoubleBuffered(RepaintManager.java:1523)
    at javax.swing.RepaintManager$PaintManager.paint(RepaintManager.java:1454)
    at javax.swing.RepaintManager.paint(RepaintManager.java:1257)
    at javax.swing.JComponent.paint(JComponent.java:1023)
    at java.awt.GraphicsCallback$PaintCallback.run(GraphicsCallback.java:21)
    at sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallback.java:60)
    at sun.awt.SunGraphicsCallback.runComponents(SunGraphicsCallback.java:97)
    at java.awt.Container.paint(Container.java:1778)
    at java.awt.Window.paint(Window.java:3390)
    at javax.swing.RepaintManager$3.run(RepaintManager.java:825)
    at javax.swing.RepaintManager$3.run(RepaintManager.java:802)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
    at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:802)
    at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:745)
    at javax.swing.RepaintManager.prePaintDirtyRegions(RepaintManager.java:725)
    at javax.swing.RepaintManager.access$1000(RepaintManager.java:46)
    at javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1668)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:672)
    at java.awt.EventQueue.access$400(EventQueue.java:81)
    at java.awt.EventQueue$2.run(EventQueue.java:633)
    at java.awt.EventQueue$2.run(EventQueue.java:631)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:642)
    at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:361)
    at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
    at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)

  9. Anton says:

    Have you fixed broken ctrl+tab navigation using arrows?
    it’s only reason why i still use 10th ws.

  10. Shawn says:

    What is the proper way to run the debugger when using a script in the npm file like in the current angular2 quickstart?

    • Ekaterina Prigara says:

      My suggestion would be to use a built-in TypeScript compiler or run “tsc” task in package.json (instead of “start” or “lite”) to build a project and then start a debug session for index.html file.

  11. Nico says:

    do you have any activation code for version 11.0.2?

Leave a Reply

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