What’s Next: WebStorm 2023.1 Roadmap

Read this post in other languages:

Last month, we rolled out WebStorm 2022.3, our final major update of 2022. We’d like to thank all of you who have already tried it and shared your thoughts with us! We’ve had an overwhelming amount of feedback, with the new UI being the absolute leader in the number of mentions.

We’re still processing your feedback to understand what worked well and what could be improved. In the meantime, we want to share our plans for the next release, which is scheduled for the end of March 2023.

Technology-specific improvements

  • Astro support. We’re going to add support for the Astro framework (WEB-52015). For starters, we want to make sure that at least the basic functionality like syntax highlighting and code completion works well. We’ll support more advanced features if there’s time for that.
  • Prisma support. Although we didn’t announce our plans regarding Prisma ORM support in the previous roadmap, we did work on adding it between the 2022.3 and 2023.1 releases. For now, the support will be available via a separate plugin, but we’ll consider bundling it next year. Please see WEB-50449 for more information.
  • Further improvements for Vue. We fixed over 40 Vue-related issues in WebStorm 2022.3. There are a few more issues we’d like to fix in the next release to improve the Vue support. We plan to provide completion for custom component events (WEB-52121) and support the type cast syntax in the template expressions (WEB-55049). Additionally, we’ll make WebStorm automatically import components and other symbols when copying and pasting template code between components (WEB-32784). This will work for Angular, too.
  • New features for Angular. In addition to WEB-32784, we want to implement two new features for Angular. For v15, we’ll add an inspection that suggests using ngSrc instead of src for img (WEB-58267). Also, symbols like enums used outside of a template or component will be automatically imported on code completion or when using a quick-fix (WEB-58268).
  • Better support for Svelte. Svelte support has been available as a separate plugin for a few years now. We haven’t been able to invest resources into Svelte much lately, so unfortunately, the quality of the support has deteriorated. We want to make sure your experience with Svelte in WebStorm is better, so we’ll try to fix the most critical issues in the next release. If you use Svelte, it’s a good time to tell us what about the Svelte support concerns you the most. Please leave a comment below, upvote the existing issues, or create a new one here.
  • Tailwind CSS plugin configuration. For Tailwind CSS, we want to make it possible to configure custom class name completion contexts (WEB-48505), custom config file path (WEB-56546), and some other options.
  • A better way to handle file references. Under the hood, there are various ways for WebStorm to handle the files referenced in your current file. For you, this might lead to various problems with performance and misleading documentation. We want to implement a more generic approach to how WebStorm handles file referencing in HTML, CSS, and JavaScript to try to solve these problems.

General improvements

  • Further work on the new UI. We’re currently processing all the feedback about the new UI and prioritizing the most critical problems. We’d like to thank you once again for reporting those problems to us and upvoting the existing issues! We’ll keep you updated on the changes that will be made to the new UI during the next Early Access Program and will ask for your feedback as we make changes.
  • Performance optimizations. We understand that WebStorm’s performance is a pain point for many of you, so we’ll keep working on fixing performance issues. We also want to look into whether there are any structural changes that could help optimize performance.
  • User onboarding. The “steep learning curve” is the other pain point we hear a lot about from those who are just starting with WebStorm. Over the past few months, we’ve been collecting information about the common problems new users have. Starting next year, we’ll be gradually reworking WebStorm’s user onboarding flow so that new users don’t feel lost or overwhelmed with the IDE.
  • Remote development improvements. A few releases ago, we introduced a new remote development workflow for all JetBrains IDEs. It has been in Beta all this time. We want to make sure we support all the important use cases before moving out of Beta. Please try the new remote development feature and tell us what you think.

That’s about it. We can’t guarantee that all these improvements will be included, but we’ll do our best to make it happen. Stay tuned for information about the upcoming bug-fix update for WebStorm 2022.3 and the start of the next round of the Early Access Program!

P.S. We’re actively looking for people to join our team. If you’d love to be a part of the WebStorm team, check out our three open positions: developer advocate, QA engineer, and senior software developer. If they sound interesting to you, please apply.

The WebStorm team

image description