WebStorm 9 EAP, 138.1988: Meteor support, Gulp and more

A couple of weeks ago we started the Early Access Program for WebStorm 9. Hopefully you are already enjoying WebStorm’s new features!

With the second EAP build we bring you more long-awaited features: support for Meteor, Gulp integration, and improved Polymer support.

Other updates include:
– support for tracing Karma tests with spy-js;
– saving and loading spy-js trace files;
– support for the latest Sass 3.4.

You can download WebStorm 9 EAP, 138.1988, from the Early Access Program page.

Meteor support

WebStorm now recognizes Meteor projects and helps you create them via the New project dialog. Code completion for Meteor API is provided thanks to a Meteor TypeScript definition file.


The key feature here is a special debug configuration for server-side Meteor code.


We’ll have a closer look at the workflow with Meteor in WebStorm in a later blog post, but feel free to try it right now and share your feedback with us.

Gulp integration


WebStorm 8 introduced Grunt support, but things are changing very fast in JavaScript world and now lots of projects are using Gulp as a build tool.

So, please welcome Gulp integration.

All tasks in your project gulpfile.js are listed in the Gulp tool window. Simply double-click the task name to start its execution.

However, unlike for Grunt integration, a new run configuration is created for every task, allowing you to run (Ctrl-Alt-R on Mac or Alt+Shift+F10 on Windows and Linux) or debug it with the familiar shortcuts.

Polymer support improvements

We’ve made improvements in Polymer support: now WebStorm better understands importing of custom elements, layout attributes and some of Polymer’s styling features. Also, the built-in debugger now stops on breakpoints inside element declaration.


For the full list of fixed issues please see the Release notes.

WebStorm 9 EAP (build 138.1988) is available for download from the Early Access Program page.

We’d really appreciate your feedback on these new features. You can post your comments here or in our issue tracker.

Please note that EAP builds do NOT require an active license and can be used for up to 30 days. To get notifications of new EAP builds as they become available, subscribe to the EAP channel in Settings | Updates.

To learn more about other WebStorm 9 features, please check these blog posts:

Develop with pleasure!
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 Cool Feature. Bookmark the permalink.

50 Responses to WebStorm 9 EAP, 138.1988: Meteor support, Gulp and more

  1. Colton McCormack says:

    Gulp and Meteor support? Finally! Been waiting for these ever since they were announced. Awesome work team, I’ll be putting it through the paces this week I’m sure.

  2. Pingback: WebStorm 9 EAP is Open! | JetBrains WebStorm Blog

  3. m_gol says:

    Wow, you’re really quick with this integrations, awesome! \o/

    Now, if only CSS updates were applied faster… CSS3 suppory is kunds lacking currently (I know, I’ve been spoiled… ;))

  4. Vladimir Varankin says:

    Nice features list! But could I ask, are there any plans for enhancing current WebStorm JSHint integration to support new features like overrides property in .jshint config. It would be very useful for general client-server project.

  5. anthony says:

    Is there any plan on adding support to Objective-J (Such as syntax highlighting, type hint, etc.)? Would love to see supports on WebStorm!

  6. Sergey says:

    Thanks very much to JetBrains team for bringing new things while fixing existing stuff – everything is very exciting. You guys rock!

  7. Anthony says:

    Looking good, EXCEPT, the new “settings” layout. Yikes! Bring back the old one!

  8. Nicolas says:

    Hi, I’m giving it a try but I’m stuck on the configuration. I can’t get webstorm to run my meteor project (and then debugging and soon).

    Where can I find information about the way to setup the server configuration for meteor?


    • Andrey Starovoyt says:

      1) Meteor project should be autodetected by .meteor folder. After detection all html files by default should be associated with ‘handlebars’
      2) Webstorm try to detect the Meteor executable. You can check that the path to executable is correct in the settings: ‘Preferences -> Lang and Frameworks -> JavaScript -> Meteor –> Meteor executable’
      3) If project is detected as Meteor project and executable is set up then the Meteor run configuration should work with default settings (it is separate item in the ‘Add new configuration’)

  9. Michał Świtoń says:

    Will all those features be available in upcoming PHPStorm 8 as well?

    • Andrey Starovoyt says:

      Gulp integration (and improved Polymer support) should be available in current PhpStorm 8 EAP (138.2071) . Meteor is available as plugin.

  10. James Wilson says:

    Thank you so much for making the best IDE even better! You guys really rock!!!

    Do you know if Coffeescript will have equal footing in Meteor support?

  11. Sergey says:

    Tutorial for spy-js with Karma would be quite useful. Thank you.

  12. zoomclub says:

    ReactJS and Webpack support?

  13. Ulrik Augustsson says:

    Gulp doesn’t seem to be able to read my gulpfile properly.
    I have a gulp.task(‘default’, [‘scripts’]); that I can run fine on it’s own but webstorm doesn’t seem to be able to pick it up.

    • Ekaterina Prigara says:

      You don’t see it in the list of available tasks in the tool window? Would really appreciate if you report it as an issue on our tracker and add a code sample.

  14. Danny says:

    No Yeoman support?

  15. Kristian Mandrup says:

    Ember.js support? Ember-CLI will be the new standard project generator by 2.0.
    Ember is ready now for some advanced IDE support. Not sure how/what exactly however (likely same reason why you haven’t focused on Ember as well…?).
    HTMLBars should land soon, which will improve/change the way handlebars work…
    ember-cli naming conventions however should make it very convenient to navigate around between controllers, models etc. since they follow very strict conventions. This could be leveraged. Also would be nice with some snippets and various type-aheads etc.
    For testing, Qunit is the default choice.

  16. Dominic says:

    I tried the meteor server debug, but the Inspector never stops at a breakpoint. Do I miss anything? I set up the Run debug config and in the console of Webstorm it says debugger listening on port 55579 and the browser starts with localhost:3000, but it never stops at any breakpoint.
    Thanks Dominic

    • Ekaterina Prigara says:

      Hello, Dominic!
      Do you have any messages from Meteor in the console in the tool window? For example, it can start doing an update…
      Have you tried to put breakpoints on any other lines in your file or in different project files? Does it stop anywhere?

  17. Pingback: WebStorm 9 EAP, 138.2406: spy-js code completion, CSS3 enhancements, Scratch files and… JSX | JetBrains WebStorm Blog

  18. Andy Fang says:

    Could you add Jekyll front-matter support for formatting SASS?

  19. Kristian Mandrup says:

    Ember.js support: Could you at least create a feature to detect an Ember CLI project and then remove /tmp and /dist from Webstorm indexing, as well as from search.

    Also, would be nice in general to have some radio boxes on global search to exclude folders such as node_modules and bower_components (or folder defined in .bowerrc)

    Thanks ;)

    • Ekaterina Prigara says:

      At the moment the workaround would be to exclude manually (folder context menu – mark as excluded) /tmp and /dist folders from the project . Would be great if you create a feature request for excluding them automatically.

      We automatically mark node_modules folder as a JS library. And starting from WebStorm 9 we index only top level modules in this folder. That decreases indexing time, while WebStorm is still able to provide code completion for functions and methods from node dependencies.

  20. Ted Goldstein says:

    Very nice. This is my first time in more than a decade than using any JetBrains product. I was attracted by the MeteorJS support. Usually I am a old-school to the metal guy. But MetorJS makes copies of things in .build directories. One really needs WebStrom to keep it together.

    One issue: It would be great to be able to set breakpoints in MeteorJS installed packages. Most packages are still under development themselves and are not well documented. MeteorJS and AtmosphereJS do a great job of distributing and installing the packages. The underlying nodejs debugger clearly knows about them. I can single step into packages. But the debugger doesn’t take accept the breakpoint.

  21. Pingback: Meteor Support in WebStorm 9 | JetBrains WebStorm Blog

  22. Daniel says:

    Love the support for Meteor. Still new to Webstorm.

    Question. I created a new ‘Meteor JS App’ using the Leaderboard template, created a Run Configuration — and it runs just fine. What do I do when I modify my code? If I try to run the configuration again I get “Can’t listen on port 3000. Perhaps another Meteor is running?”. How can I close the already running Meteor that Webstorm automatically starts up for me and re-start? Or — is there a better way to do this?

Leave a Reply

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