What’s Next: WebStorm 2020.2 Roadmap

This year’s first major update, WebStorm 2020.1, landed a couple of weeks ago. We’d like to thank everyone who shared their product experience, feedback, and suggestions with us during our Early Access Program. You helped us make v2020.1 better!

With WebStorm 2020.2 scheduled for the end of July, we’ll continue to move in the same direction that we designated at the end of last year.

First, we’ll keep improving performance. We’re currently working on several platform-wide initiatives that we announced last year, including less disruptive indexing and dynamic loading of plugins. To learn more about these and other performance-related initiatives we have planned for 2020, take a look at this blog post.

As usual, you’ll also find lots of new features and improved support for some technologies in WebStorm 2020.2. For starters, we’re still experimenting with ML-assisted code completion for JavaScript and TypeScript. We’ll share more details about it as soon as we get some meaningful results.

For the frameworks, we want to implement some basic support for Nuxt.js, teach the IDE to better recognize CSS modules in Vue projects, and further improve support for React Redux.

We’ve also been getting a lot of questions about Svelte.js support. Although we don’t plan to add out-of-the-box support for it at the moment, we’ve decided to collaborate with the author of the popular Svelte plugin, who has already done outstanding work on it, in order to help enhance Svelte support available with this plugin. As soon as our collaboration brings some tangible results, we’ll publish a blog post explaining how you can get the most out of this plugin.

You can also expect some long-awaited improvements to JavaScript tooling. Some of them, including WSL support and an option for running ESLint on save, will be already available in the upcoming bug-fix updates for WebStorm 2020.1. In addition to that, we want to add an option to set Prettier as the default formatter.

Lastly, we’ve already done some housekeeping activities in the previous release cycle but we have some more planned for the next few months. Specifically, we’ll keep deprecating support for some rarely used technologies and tools. This doesn’t mean you will lose the support for them, but it will stay available via plugins.

That’s about it. Of course, our roadmap is subject to change, but the overall direction will stay the same. Stay tuned for the upcoming start of the Early Access Program for 2020.2!

The WebStorm team

About Ekaterina Ryabukha

WebStorm Product Marketing Manager at JetBrains
This entry was posted in General Announcements and tagged , . Bookmark the permalink.

30 Responses to What’s Next: WebStorm 2020.2 Roadmap

  1. Aparajita Fishman says:

    Eslint on save! Finally!

  2. Mladen says:

    “In addition to that, we want to add an option to set Prettier as the default formatter.” No, please don’t do this. When you open prettier.io, it says that it is “An opinionated code formatter”. And it really is, an opinionated code formatter which we tried in our projects and literally no-one liked it, so we removed it.
    I would be OK if Prettier is the default formatter only if it’s imported to the project with package.json, but if it’s not, please keep the default WebStorm formatter.

    • Igor Savin says:

      1) It’s an option;
      2) Your team seems to be in minority. In last 4 teams that I was, everyone liked it, so YMMV.

      • Juan says:

        As long as it is optional that should be ok. There are teams like one Mladen talks about which don’t like it, 49% is also a minority in some way ;)

  3. Vojtech says:

    What about a color emoji support? It is now few years that we wait for something other IDEs have.

    https://youtrack.jetbrains.com/issue/JBR-410

  4. Tomas says:

    Sounds great, what type of improvements were you planning for React Redux users?

    +1 on Prettier as default formatter option. +100 if you’ll set that automatically based on our project’s package.json, so that it’ll all just work out of the box for every user on our team.

  5. K3N says:

    You’re doing great guys. Looking forward to even more improvements and sveltejs.plugin improvements as well. Cheers!

  6. Guido Mista says:

    Is WSL support do you mean it is WSL 2?

  7. Mitchell says:

    WSL Support? Would love to know what this might look like.

  8. XIAOFENG XIE says:

    It would be great if you guys can add native support for code collaboration like VS LiveShare.
    Especailly, this feature becomes more important during this crisis.

    • Ekaterina Ryabukha says:

      We’re currently working on implementing some features for collaborative editing. We’ll share more information about it as soon as we get some meaningful results.

  9. RAJIB HALDER says:

    “Eslint on save” is a feature i am waiting for. In EAP version, how can i enable it on save ? I have downloaded the EAP version in my local.

    I have already enable “Prettier on save”. How to arrange order so that “Eslint” will always execute after “Prettier” ?

    • Ekaterina Ryabukha says:

      Hello,
      To enable this option for the current project, go to Preferences/Settings | Languages and Frameworks | JavaScript | Code Quality Tools | ESLint and tick the Run eslint –fix on save checkbox. To turn the new option on for all new projects, from the main menu go to File | New Project Settings | Preferences/Settings for New Projects and tick the same checkbox. Either way, don’t forget to disable the file watcher you’ve been using for this purpose.
      As for your second question, it’s not possible to arrange the order at the moment. If both tools were enabled on save using these checkboxes, they would contradict each other. We plan to implement global save actions in our IDEs. When they are implemented, it’s likely that there will be an option to arrange the order.

  10. Michael Talbot says:

    Super excited for more Svelte support, that would be excellent. ML in Javascript also sounds fascinating.

    I’d dearly love to be able to get our formatters fully lined up though on save. I keep getting problems where they fight and everything is dirty after a commit that did optimised imports etc. Seems that I still can’t get the internal formatter to fully respect our Prettier options.

    • Ekaterina Ryabukha says:

      Hi Michael,
      We’re happy to hear that you feel excited about the upcoming updates! As for the issue with formatters, it would be great if you could share more details with our support team: https://intellij-support.jetbrains.com/hc/en-us/requests/new. They will see whether the current behavior can be improved somehow and, if it’s related to a bug or a missing feature, will file a new issue for that.

  11. Christopher Rucinski says:

    Can you please extend licensing support for all non-community IDEs until the 2020.2 EAP release? While I can probably apply for open-source license as I’m experiencing session-reducing limitations, this would be a nice gesture during these times.

  12. Juan M Menendez says:

    What about liquid support?

  13. Rafik Ogandzhanyan says:

    1Please, improve Vue support:
    1) Vue + TS in Vue.component \ Vue.extend
    2) Vue components with template\style files (not one-file component)

    Thank you.

Leave a Reply

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