What’s Next: WebStorm 2020.2 Roadmap

Posted on by Ekaterina Ryabukha

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

Comments below can no longer be edited.

34 Responses to What’s Next: WebStorm 2020.2 Roadmap

  1. Aparajita Fishman says:

    April 21, 2020

    Eslint on save! Finally!

    • Ekaterina Ryabukha says:

      April 22, 2020

      If you’d like to, you can already try it out by downloading the RC build for v2020.1.1 from here: https://confluence.jetbrains.com/display/WI/WebStorm+EAP or using the Toolbox App.

      • Pavel Kaminsky says:

        May 5, 2020

        one suggestion if I may, the “eslint –fix” on save should run in background by default.

    • Igor says:

      April 22, 2020

      I wanted this feature for a long time. However, I just bound Eslint fixes to alt + s, which is close on the keyboard to ctrl + s. You can do that under Keymap -> Eslint on save.

      • ano says:

        April 27, 2020

        What? Webstorm has long been able to use eslint when saving. Go to file watcher section in “preferences”. There are even ready-made templates there. You can also enable prettier there.

  2. Mladen says:

    April 22, 2020

    “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:

      April 22, 2020

      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:

        May 11, 2020

        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:

    April 22, 2020

    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

    • Ekaterina Ryabukha says:

      April 23, 2020

      We’ve started working on. Unfortunately, we cannot provide any ETA at the moment.

  4. Tomas says:

    April 24, 2020

    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:

    April 25, 2020

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

    • Ekaterina Ryabukha says:

      April 27, 2020

      Thanks! We’re glad to hear that you like our planned improvements.

  6. Guido Mista says:

    April 26, 2020

    Is WSL support do you mean it is WSL 2?

  7. Mitchell says:

    April 27, 2020

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

  8. XIAOFENG XIE says:

    April 27, 2020

    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:

      April 28, 2020

      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:

    April 29, 2020

    “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:

      April 30, 2020

      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:

    May 11, 2020

    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:

      May 12, 2020

      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:

    May 11, 2020

    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.

    • Ekaterina Ryabukha says:

      May 12, 2020

      Hello Christopher,
      Please reach out to our community support at community-support@jetbrains.com, they can help you with applying for an open-source licence and look into a more specific inquiry like extending a paid license.

  12. Juan M Menendez says:

    May 15, 2020

    What about liquid support?

  13. Rafik Ogandzhanyan says:

    May 29, 2020

    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.

    • Ekaterina Ryabukha says:

      May 29, 2020

      Hi Rafik,
      Improving Vue support has been one of our main goals for the last few releases, and this release is not an exception.
      Some new improvements, including proper resolution of data properties for components created with Vue.extend() when using single-file components, are already available in v2020.2 EAP. You can read about the latest improvements here: https://blog.jetbrains.com/webstorm/2020/05/webstorm-2020-2-eap-1/. A more comprehensive list is available here: https://confluence.jetbrains.com/display/WI/WebStorm+202.4357.21+Release+Notes.
      Some other improvements are coming soon. If you’d like to know whether we plan to fix a specific issue during this release cycle, please share the link to it with me, I’ll let you know what our plans are for it.

      • Reznik Artem says:

        June 4, 2020

        Would be nice to hear any news about https://youtrack.jetbrains.com/issue/WEB-41084
        Thank you for the nice IDE!

        • Ekaterina Ryabukha says:

          June 5, 2020

          Hi Artem,
          This issue is part of a larger task we’re currently working on – improvements for template and JS/TS code completion and resolution specific to Vue.js. Unfortunately, I can’t say for sure whether this specific improvement will make it to v2020.2 as there are quite a lot of issues related to that task, please keep monitoring the issue for updates.

      • Rafik Ogandzhanyan says:

        June 5, 2020

        Thank you for your answer.

        Is this task will also come to 2020.2 https://youtrack.jetbrains.com/issue/WEB-44150 ?

        • Ekaterina Ryabukha says:

          June 5, 2020

          Hi Rafik,
          Just like it is with the issue that Artem asked about above, the WEB-44150 issue is also part of a larger task we’re currently working on – improvements for template and JS/TS code completion and resolution specific to Vue.js. Unfortunately, I can’t say for sure whether it will make it to v2020.2 as there are quite a lot of issues related to that task, please keep monitoring the issue WEB-44150 for updates. Hopefully, it does make it to v2020.2 or at least to bug-fix updates for it 🙂