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

🎉 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

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.

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

  1. Alexei Artemiev says:

    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?

  2. Mart Sõmermaa says:

    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.

  3. Andrey Grinkevich says:

    Any update for 12-year old feature request?

  4. Wade Liu says:

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

  5. Jose Marquez says:

    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…

  6. Michael Snead says:

    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!

Leave a Reply

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