WebStorm 2017.3: improved Vue.js support, new refactorings, new REST Client, and more

Ekaterina Prigara

🎉 Today we’re announcing WebStorm 2017.3  🎉

This big update brings improvements to all parts of the IDE, from support for JavaScript, TypeScript, and the frameworks to debugging and testing.


Here are the key highlights of WebStorm 2017.3 that you can’t miss:

  • Enjoy improved code completion and documentation for standard JavaScript
    objects and methods.
  • Move class methods up the class hierarchy safely with the new ‘Pull member
    up’ refactoring
  • Use the new ‘Extract type’ and ‘Extract interface’ refactorings in TypeScript.
  • Enjoy better code completion and navigation and new code snippets for
  • Run tests with Jest in watch mode, update failing snapshots in one click, and
    explore code coverage reports in the IDE.
  • Test REST APIs right from the editor.

Explore the new features and download WebStorm 2017.3 on our website.

Download WebStorm 2017.3

WebStorm Team

Comments below can no longer be edited.

19 Responses to WebStorm 2017.3: improved Vue.js support, new refactorings, new REST Client, and more

  1. Alexei Artemiev says:

    November 28, 2017

    Hello! Great news! Will it be possible to update from within the IDE and when? Or no patch will be available for this update, only standalone installer?

    • Ekaterina Prigara says:

      November 28, 2017

      Hi! There’s a patch update available for WebStorm 2017.2.5 and 2017.3 RC.

  2. Mart Sõmermaa says:

    November 29, 2017

    Really happy for improved Vue.js support, many thanks for making it happen!

    Vuetify tags are unfortunately still not recognized, WebStorm shows ‘Unknown HTML v-card-title’ etc.



    Vuetify is one of the top Material Design component frameworks for Vue.js (6800 GitHub stars), so it is worth supporting.

    • Ekaterina Prigara says:

      November 30, 2017

      Thanks for the links. We’ll have a look.

  3. Andrey Grinkevich says:

    December 4, 2017

    Any update for 12-year old feature request?

    • Ekaterina Prigara says:

      December 5, 2017

      Sorry, don’t know anything about that.

  4. Wade Liu says:

    December 7, 2017

    Keymap Extend Selection in in *.vue files didn’t work successfully.So I have to use 2017.2.5……

    • Wade Liu says:

      December 7, 2017

      in script tag

  5. Jose Marquez says:

    December 7, 2017

    Since updating to 2017.3, WebStorm warns me about lines like:
    import * as actions from ‘./’
    saying it can’t resolve the (index.js) file.
    I can eliminate the warning by explicitly importing the index, but this seems like a behavior I should be able to configure around rather than making hundreds of edits to my code:
    import * as actions from ‘./index’ <== no warning
    Is it possible to not trigger these warnings? I can't find an inspection specifically requiring that we explicitly name the index even if it's implied from a directory name…

    • Ekaterina Prigara says:

      December 11, 2017

      we’ve reported the problem on our tracker: https://youtrack.jetbrains.com/issue/WEB-30209
      Please follow the issue for the updates. As a workaround you can disable the “Validate file reference” inspection in Preferences | Editor | Inspections.

  6. Michael Snead says:

    December 10, 2017

    Hi, there. As a happy customer and evangelist for WebStorm, I’d like to ask that you please put this feature on your backlog/roadmap!

    I have very much enjoyed the bind operator supported by WebStorm ( :: ), but it looks like the pipeline operator proposal is the one the tc39 committee is deciding to move forward on ( |> )… Your rapid support and adoption of tech has been nothing short of amazing time and again. Thank you for this great product!

    • Ekaterina Prigara says:

      December 11, 2017

      Hi Michael, we’re keeping an eye on this proposal. We might support it in WebStorm 2018.1.

      • Michael Snead says:

        December 11, 2017

        I’m excited and hopeful! Thanks for the reply!

      • Carlos Guimaraes says:

        January 26, 2018

        Maybe on 2018.2? fingers crossed…

      • Anatoly Leskovets says:

        November 16, 2018

        Hey Ekaterina,

        Any updates on that feature?

        • Ekaterina Prigara says:

          November 19, 2018

          Sorry, we don’t plan to support it while it’s still in the Stage 1 and there are still the ongoing discussions about its syntax.