blog.jetbrains.com

What’s Next: The WebStorm 2025.2 Roadmap

In April of this year, we released WebStorm 2025.1, our first major update for 2025. Thank you to everyone who is already using it and providing feedback. With April now behind us, we’d like to announce what we’ve got planned for the next release of WebStorm, which is scheduled for July, with our usual disclaimer: […]

May 23, 2025 - 18:00

What’s Next: The WebStorm 2025.2 Roadmap

In April of this year, we released WebStorm 2025.1, our first major update for 2025. Thank you to everyone who is already using it and providing feedback.

With April now behind us, we’d like to announce what we’ve got planned for the next release of WebStorm, which is scheduled for July, with our usual disclaimer: these plans are subject to change.

Also, as usual, EAP builds are available in the run-up to this release. We encourage you to try these builds, provide feedback on the features, and report any issues you discover. At this stage, you can significantly impact the product’s development.

Here are our most significant plans for WebStorm 2025.2:

Bun

In the 2025.2 release, we’re working on WebStorm’s Bun experience, with new features that make it easier to get up and running:

Automatic detection: If your project includes a bun.lockb file, WebStorm will automatically detect it and suggest using Bun as your package manager. No manual setup needed.
Context-aware actions: You’ll be able to run files using Bun directly from the context menu, just like you would with Node.js.

These changes are part of our broader effort to support alternative runtimes and package managers out of the box – giving you more flexibility to choose the tools that work best for your stack (WEB-67011).

Service-powered type engine

Over the past few releases, we’ve been building out a new service-powered type engine – a behind-the-scenes revamp of how WebStorm understands and processes TypeScript types. While we’ve already shipped parts of it in earlier versions, WebStorm 2025.2 will continue this journey by focusing on improving performance.

Improving performance in large frameworks: We’re aiming to make type inference and code completion faster and more reliable, especially in projects that use complex setups or extensive component hierarchies. Right now, we’re working on improving tag and attribute completion in React (TypeScript), as well as Angular templates – two areas where traditional language services can struggle to keep up.
Fixing edge cases with third-party libraries: One notable fix we’re working on addresses missing props from libraries like motion when the new engine is enabled (WEB-72440).

CSS

CSS is evolving quickly, and we want to make sure WebStorm evolves with it – so you can take full advantage of the latest syntax and styling capabilities without sacrificing the confidence that comes from strong code assistance.

In WebStorm 2025.2, we’re focusing on two main areas:

Support for modern CSS features – We’re enhancing WebStorm’s CSS engine to recognize fresh property values, newly introduced at-rules, and updates from the CSS Color Module, including the ability to parse and validate newer color formats. Whether you’re using @layer, :has(), or working with color functions like color-mix(), you’ll benefit from more accurate validation, completion, and syntax highlighting (WEB-70107).
Fix for CSS variables in language injections – A long-standing issue with CSS variables not resolving correctly inside language-injected code (like styled-components or other CSS-in-JS scenarios) is being addressed. This means cleaner, more accurate styling support across JavaScript, TypeScript, and HTML templates, without losing insight when working with embedded styles (WEB-38704).

These improvements aim to make styling in WebStorm feel just as modern and powerful as the frameworks you’re building with – whether you’re using traditional CSS or the latest CSS-in-JS approaches.

TypeScript

The TypeScript team recently announced a major initiative: rebuilding the TypeScript compiler and language service in Go. This new “native” architecture is designed to unlock faster performance.

While this native rewrite is still in its early stages, we’re already taking steps inside WebStorm to prepare for what’s coming.

You won’t see visible changes from this just yet, but this groundwork is essential for staying aligned with the future of the TypeScript ecosystem.

That’s all for now! Join the 2025.2 Early Access Program to test out these features as they become available!

The WebStorm team