WebStorm 7 EAP

Posted on by Dmitry Jemerov

Here at the Fluent conference in San Francisco, we’re happy to announce the release of the first Early Access Preview build of WebStorm 7. The new features so far include:

  • Completely redesigned JavaScript debugger backend for Chrome based on WebKit Remote Debugging Protocol, as well as for Node.JS based on the V8 protocol
  • Simplified Node.js remote debug — you don’t need to specify local directory and remote path.
  • Integration with Karma test runner (note: currently works only with karma@canary, the latest development version)
  • Bundled plugin for Mustache and Handlebars templates support
  • Initial support for Web Components
  • New structure view for less/sass/scss
  • Breadcrumbs in less/sass/scss
  • Suppressible inspections in css/less/sass/scss
  • New css intentions for colors conversion
  • Configurable built-in web server port (issue WEB-6998)
  • Built-in web server supports custom host name
  • Debugging asynchronously loaded js content is possible, we support jquery.getScript (issue WEB-2442)
  • New JavaScript intentions: “Convert for loop to forEach call on array”, “Simplify array creation”
  • Improved completion for parameters of getElementById()
  • Code insight support for package.json files
  • Internal refactorings and code cleanup to enable faster development of new features and framework integrations

The build is available for download now from the EAP page. Your feedback is, as usual, welcome in the issue tracker. And if you’re currently at Fluent, please come by our booth in the expo hall and tell us what you think about the new features and what else you’d like to see in the final 7.0 release in September.

Comments below can no longer be edited.

22 Responses to WebStorm 7 EAP

  1. Greg says:

    May 29, 2013

    Awesome, will the asynchronously loaded js content work with require js?

    • Vladimir Krivosheev says:

      May 29, 2013

      requirejs uses normal way to load script, so, requirejs doesn’t need special support.

  2. Jeff Schwartz says:

    May 30, 2013

    Awesome. I really feel sorry fo all those sublime groupies lol.

  3. interfaSys says:

    May 30, 2013

    Will v7.0 finally support Sencha Touch / ExtJS?

    • Dmitry Jemerov says:

      May 30, 2013

      What exactly do you mean by “finally support”? We do have quite a few features in our code insight functionality to support ExtJS.

      • Christian says:

        May 30, 2013

        While it does work better then other IDE it still lack some core information. Like their namespace and class definition. You can’t open a class with alt+n that was defined with Ext.define(). Structure panel also need some tweak, you always have to expand each node of a name space.

      • interfaSys says:

        May 31, 2013

        I was referring to:
        WEB-1160
        WEB-1276
        WEB-1109
        WEB-1501

        Which were all supposed to be delivered in 6.0 and got cancelled at the last minute.

        I see now that WEB-1501 has landed and hopefully the rest will follow.

        • Dawesi says:

          September 13, 2013

          +1

        • Vikram says:

          November 15, 2013

          Yes please add extensive exclusive support for ExtJS and Sencha code framework auto completion and IDE shortcuts and documentation references.

  4. Francesco Maida says:

    May 30, 2013

    You ROCK. As usual 🙂

  5. Vivian Cromwell says:

    May 30, 2013

    I haven’t played with the new EAP yet, can you elaborate a bit on the initial support for web components?

  6. Ian Battersby says:

    May 30, 2013

    I’m seeing issues with the karma runner when parsing our config files, initially that the call to slice() on plugins fails as that isn’t in our config files. Changes this to use the “files” array resolves that but then the reporter can’t be found.

    Could you link to a gist of an example config file to I can compare difference?

    • Sergey Simonchik says:

      May 30, 2013

      Make sure you are using karma@canary (at the moment its version is 0.9.2) and your karma.conf.js has been regenerated using “karma@canary init” command.
      If you still have the problem, please file an issue in the http://youtrack.jetbrains.com/issues/WEB#newissue=yes (subsystem: Unit Tests) and attach there exception stacktrace.
      Thanks.

  7. WebStorm 7EAPのkarma連携について | Web scratch says:

    June 1, 2013

    […] WebStorm 7 EAP がリリースされましたが、今まではJsTestDriverぐらいしかテスト連携のサポートは入っていませんでしたが、karmaのサポートが追加されました。 […]

  8. Tom Lanning says:

    June 3, 2013

    Can the Karma test runner be used in other products like Rubymine?

    • Dmitry Jemerov says:

      June 3, 2013

      Not right now, but in the future it will be either bundled into RubyMine or made available for download through the plugin manager.

      • Jason Weden says:

        July 29, 2013

        Will the Karma test runner support be part of the corresponding intellij idea plugin?

        • Dmitry Jemerov says:

          July 30, 2013

          The Karma plugin has already been released to the plugin manager. It’s a separate plugin that requires IntelliJ IDEA 13 EAP.

  9. Eugene says:

    June 27, 2013

    Is there any plans to support Stylus css preprocessor?

  10. AngularJS, Karma and debugging unit tests in WebStorm or IntelliJ IDEA | mariuszprzydatek.com says:

    July 21, 2013

    […] offer native Karma test runner support (ver 7 which is currently in EAP, does – details here), but using a NodeJS plug-in you can execute any kind of NodeJS application (Karma […]