WebStorm 12 roadmap and EAP

Time flies fast and we are already starting the Early Access Program for the next major WebStorm release. You can download WebStorm 12 EAP, build 144.2608, right now. You can install it side by side with WebStorm 11. No active subscription is required.

While we don’t have that many new features to show you right now, we hope you’ll try out some of the improvements (like support for the new Angular 1.5 Component helper and code insights for Angular 2 bindings), performance fixes for JavaScript and numerous fixes that have already landed in WebStorm 12 EAP.

Also, with this being a perfect time for New Year’s resolutions, we would like to share with you our plans for the next couple of months.

Better coding assistance for JavaScript, ECMAScript and TypeScript

We’re always working on improvements in language support, but this time we want to allocate some extra time to work on refactoring options available for JavaScript, ES6 and TypeScript. And of course, performance is always our top priority: we hope to deliver faster indexing for big JavaScript projects, faster code completion results, and more.

Your CPU snapshots showing any IDE performance issues are always very welcome and appreciated.

Keeping up with the frameworks: React, Angular 1.5 and 2

With so many great frameworks around and already supported in WebStorm, we want to make sure that WebStorm users can get the best coding assistance for them with support for all the latest features. As we see a big (and growing) interest in React in the community and the strong position of Angular, we want to further improve support for these frameworks in WebStorm with more smart features.

There are also some things on our list that had been planned for but unfortunately did not make it into WebStorm 11. We have revised some of the initial ideas and hope to start working on some of them in the nearest future:

Next steps in npm support improvements
WebStorm 11 included npm script integration and some npm-related inspections in code. Now it’s time to add coding assistance for packages and their versions in package.json, and to support various scenarios of managing project Node.js dependencies from the IDE.

Webpack support
While we’ve made WebStorm able to debug apps built with Webpack, we’re still thinking about the best way to support Webpack-specific require statements.

Running and debugging Node.js applications remotely
We’d like to add an option to run Node.js applications remotely from the IDE and debug them. We have already started working on a remote run via SSH on a remote machine and then we plan to enhance the feature with the integration with Docker and Vagrant.

Other things that we are considering and may work on include:

  • Options to run and debug Electron applications
  • support for CSS variables
  • further Flow integration (if it becomes available for Windows)
  • deeper integration with build tools (may be some new workflow that could replace the File watchers), and more.

We want to hear your opinion before deciding which of these features will be implemented in WebStorm. So, our issue tracker is always open for your feature requests (and bug reports). Let us know what you think!

Read about the features and improvements added in the recent WebStorm 12 EAP builds:

  • WebStorm 12 EAP, 144.3600: Support for Git worktrees, updated look and feel of the Git Log, Missing import statement inspection for JavaScript.
  • WebStorm 12 EAP, 144.3357: SSH Console, Extract field refactoring in TypeScript, support for debugging Node.js apps built with Webpack, and more.
  • WebStorm 12 EAP, 144.3143: Unused imports warning, code assistance in tsconfig.json, .babelrc and .eslintrc, remote run and debug for Node.js apps, Vagrant integration, debugging Electron apps, and further improvement in Angular 2 support.
  • WebStorm 12 EAP, 144.2925: Inline rename, smarter auto-imports and Optimize imports action for TypeScript, debugging async client-side code, and improvements in Angular 2 support.

– 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 Early Access Preview, General Announcements. Bookmark the permalink.

49 Responses to WebStorm 12 roadmap and EAP

  1. Nikita says:

    Thanks, that’s an inspiring plan. Do you plan to enhance facebook flow support in v12?

  2. Marek says:

    No mention about Vue.js support :( Maybe later? ;)

  3. Matt says:

    Getting: “Cannot start under Java 1.6.0_65-b14-468-11M4833: Java 1.8 or later is required.” when manually trying to change JDK to 1.6 on OSX 10.11. Its a known issue that Webstorm is terribly slow under Java 1.8+ on Mac with the custom JDK, is it possible to bundle for 1.6 – or are there going to be some serious performance improvements to make Webstorm usable under 1.8 – as at this point its a big regression in terms of performance?

    • Dennis Ushakov says:

      As far as we know, Java 1.8 specific problems have been resolved. Please try running v12 EAP with default bundled Java and report any problems if you encounter them

  4. Pavel Klimashkin says:

    And don’t forget about ES7, at least starting from stage 1

  5. Ozum says:

    Hope to see flow support especially comment style flow declarations (http://flowtype.org/blog/2015/02/20/Flow-Comments.html)

  6. Elijahu Malka says:

    thank you for this post, what about RTL support for the editor?

  7. How do you keep track of how many users use this or that external tool or framework? If you don’t, please do. When/if you do, please make the statistics publicly available. Apart from being merely “interesting”, to see what other people are using, it will help tremendously with posts “Why don’t you support XYZ”, because when people see that XYZ is used by only 0.1% of users they’ll not be nearly so loud or annoyed, and if it’s the opposite it’s good too.

    Because I, as someone who uses very few of stuff like Typescript, React, Angular (in all its versions), Bower, etc etc (and npm only on the command line) I am MUCH more interested in getting the bugs in the base system fixed compared to all the new stuff. And what I said above is valid for me too: If I see 2/3 of all users need those functions then *I* will (grudgingly) accept priorities on new functions, but if it turns out there’s <5% of users for each of those things I'll yell more loudly/often… :)

    • Ekaterina Prigara says:

      Hello,
      Yes, sure we keep track of the trends in the web development. Some of the sources we rely on include various developer surveys like those by DailyJS (last year we analysed the results for WebStorm and IJ users and shared that in our blog) and this year by ponyfoo.

      We also keep track of numbers of stars, forks on GitHub, questions on StackOverflow, downloads from npm, etc for various tools and frameworks and how these numbers change.

      Votes for the issues on YouTrack are also really count. As well as the number of downloads for plugins in our other IDEs (not all web-related features work in our other IDEs out of the box, users have to install plugins).

      That’s not that easy as you say: we can’t rely only on the numbers at the current moment. It takes time to provide support for the technology, if we start working on that only at the moment when we know for sure that at least 2/3 of the web developers use that, it means that it’s too late already – by the time we finish all people switch to different editors and IDEs. We need to be one step ahead.

      Working on the bug fixes is always a bigger part of our every day job, trust us, but with the fast evolving ecosystem and in general growing interest in web development we can’t ignore the new things coming.

  8. Yehor says:

    Yay! When to expect final release?

  9. maruo says:

    I’m surprised system.js and jspm are not mentioned. No plan yet?

    Request for system.js:
    https://youtrack.jetbrains.com/issue/WEB-13064

    Request for jspm:
    https://youtrack.jetbrains.com/issue/WEB-18904

    • Ekaterina Prigara says:

      No precise plan for that, but we’ll try to do something with that.

      • Paolo says:

        Hi Ekaterina,
        writing just to point out that Angular 2 team is suggesting the use of System.js in their official tutorials, and I think they are already using it in production..
        In addition, JSPM proves to be the “easiest” choice for System.js users, and it has been adopted officially by many cutting edge frameworks (see Aurelia, a great Angular 2 contender).
        You said that u have to be ahead of the competition, so I think that supporting System.js right in the upcoming version will make future Angular 2 users very happy.
        (PS: I’m currently working with System.js and JSPM in production with Aurelia, and starting now a new project with Angular 2 AND System.js/JSPM)

        Just my 2c..
        Paolo

  10. sf says:

    CPU snapshots link is broken

  11. Vasyl says:

    WebStorm 11 was good. But this roadmap is simply amazing! Good direction. Please, keep it up! I like every choice you did this time.
    Cheers

  12. Dan Lourenco says:

    How about Aurelia support? That’s been a highly requested feature in the forums.

  13. Peter Kalkman says:

    What about JSPM (jspm.io) support in WS 12? I read about Webpack, but no mention of JSPM.

  14. Mike says:

    Could you please clarify what is the difference between IDEA 16 EAP and WebStorm 12 EAP?

    Both of them have 144.2608 build number.
    Can I benefit from all features of WebStorm 12 EAP in IDEA 16 EAP and vice-versa (in a frame of features set of the WS IDE)?

    • Ekaterina Prigara says:

      IntelliJ IDEA has all the WebStorm features available out-of-the-box or via plugins. As we add more web-related features in WebStorm 12 EAP, they are also going to be available in IJ 16 EAP published after that.

  15. Hi,

    I’d like to see continuous efforts for debugging es6/es7 applications.
    While it is working in theory, in reality medium to larger projects (starting with a few hundred lines of code) start crashing, never finish or just return stupid stuff.

    Regards
    Stefan

    • Ekaterina Prigara says:

      Hi, we’re constantly working on various debugger-related issues. All the projects are very different – using different tools to compile and bundle code and generate source maps, because of that we sometimes overlook some problems. Would be really helpful if you report an issue on our tracker describing the problems you have: https://youtrack.jetbrains.com/issues/WEB Thank you!

  16. ramuscwalk says:

    So, our issue tracker is always open for your feature requests (and bug reports). Let us know what you think! Where such information?

  17. Mark says:

    What about EMBER JS? How long do we have to wait for you to take your chance to support this framework?

  18. Dmitry says:

    I don’t understand why Python, Ruby, PHP developers get Database Tools and SQL since 2012 and node.js developers don’t. Can’t see logic here, and the corresponding issue in the tracker has ‘won’t fix’ status https://youtrack.jetbrains.com/issue/WEB-6171

    Could someone elaborate on this?

    • Ekaterina Prigara says:

      Here’s a link for a corresponding feature request and it’s opened: https://youtrack.jetbrains.com/issue/WEB-13293
      We treat this feature as any other feature on our issue tracker, at the moment we don’t feel that there’s a huge user demand and we don’t plan to add it in the upcoming WebStorm 12. Moreover, at the moment the Database tools available in other JetBrains IDEs don’t have support for NoSQL databases such as MongoDB that is most often used with Node.js. Please vote for the issue and follow the status updates. Thank you!

  19. Marc Smith says:

    +1 for Database Tools and SQL
    is there still not a demand for this? there seems to be a decent amount of search results/discussion for this issue. :-/

  20. Shlomi Assaf says:

    Regarding Webpack support:

    https://youtrack.jetbrains.com/issue/WEB-17533

    Is very important, we get such a great power from being able to define custom lookup directory for module (“node_modules”) which allows creating inner packages without the hassle of npm’ing them and soft linking all around, this is a much appreciated feature.

  21. Juan says:

    Jetbrains I will like to see a wordpress plugin for webstorm, because front-end. :D

  22. Birowsky says:

    I’m quite dazzled that there is still no plan for Elm.

  23. Jan Zelenka says:

    Flow is now officially supported on windows:
    https://flowtype.org/blog/2016/08/01/Windows-Support.html

    any update to webstorm’s flow roadmap because of this?

    Thanks.

    • Ekaterina Prigara says:

      Thanks! WebStorm 2016.2 has been released about a month ago, we haven’t yet finalised the WebStorm 2016.3 roadmap. Please follow the blog for updates.

Leave a Reply

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