round()<\/code>, rem()<\/code>, and mod()<\/code>.<\/li>\n\n\n\n- Unified <\/strong>JavaScript Runtime<\/em><\/strong> settings page<\/strong> that consolidates Node.js, Bun, and Deno configuration.<\/li>\n\n\n\n
- Vitest 4 support<\/strong>, enabling the correct discovery and execution of tests written for the latest Vitest version.<\/li>\n<\/ul>\n\n\n\n
This release also includes numerous fixes and quality\u2011of\u2011life enhancements for TypeScript, Angular, Vue, Astro, Prettier, and more.<\/p>\n\n\n\n
You can update to WebStorm 2025.3 via the Toolbox App or download it directly from our website. We can\u2019t wait for you to try it. Please let us know what you think \u2013 your feedback helps make WebStorm better with each release. Happy coding!<\/p>\n\n\n\n
DOWNLOAD WEBSTORM 2025.3<\/a><\/p><\/p>\n\n\n\nKey improvements<\/strong><\/h2>\n\n\n\nTypeScript <\/strong><\/h3>\n\n\n\nService\u2011powered type engine <\/h4>\n\n\n\n
The experimental type engine introduced via the WebStorm@next program now has an official name: the service\u2011powered type engine<\/strong>. This engine delegates type evaluation to the TypeScript language service instead of WebStorm\u2019s internal type resolver. It generally reduces CPU usage, improves performance in many scenarios, and ensures better compatibility with native TypeScript behavior.<\/p>\n\n\n\n
Starting from 2025.3, this engine will be enabled gradually for a subset of WebStorm users. Other JetBrains IDEs remain unchanged, so their TypeScript experience is not affected. A status bar widget indicates the engine status, and you can also submit bug reports from this widget.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/12\/image-3.png\" "\\"Service-powered")
<\/figure>\n\n\n\nBetter module resolution and monorepo support<\/h4>\n\n\n\n
WebStorm 2025.3 uses the customConditions<\/a> property in tsconfig.json<\/code> and \u201cdevelopment\u201d conditions in exports<\/code> fields to support<\/a> build\u2011free editing (see the Node.js documentation<\/a>). This means auto\u2011imports, Go to Definition<\/em>, and Find Usages<\/em> work without building output directories. The automatic import mechanism has also been improved for pnpm symlinked packages. To ensure TypeScript correctly detects workspace packages, we suggest using explicit exports<\/code> entries and moduleResolution:\"nodenext\"<\/code> (WEB-74887<\/a>).<\/p>\n\n\n\nDetecting out\u2011of\u2011memory errors in the TypeScript service<\/h4>\n\n\n\n
Large TypeScript projects can occasionally trigger out\u2011of\u2011memory (OOM) errors in the TypeScript language service. To help you diagnose and resolve these issues, WebStorm now monitors stderr<\/code> output for specific OOM messages and presents a notification suggesting that you increase the service\u2019s heap size.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/12\/detecting_out_of_memory_errors_in_TS_service.png\")
<\/figure>\n\n\n\nFile extension handling and .mts support <\/h4>\n\n\n\n
Several long\u2011standing issues with module extensions have been resolved. A fix<\/a> in WebStorm 2025.2.3 and 2025.3 prevents .mjs<\/code> files from replacing .mts<\/code> in auto\u2011imports. There is also a proposal to honor TypeScript 5.0\u2019s allowImportingTsExtensions<\/code> flag via Code Style | TypeScript | Use file extension = \u201cAuto\u201d<\/em>. With this configuration, .ts<\/code> or .js <\/code>will be chosen automatically based on your moduleResolution<\/code> setting and whether allowImportingTsExtensions is true<\/code> (WEB-60748<\/a>).<\/p>\n\n\n\nAI Assistant: Junie and Claude Agent integration<\/strong><\/h3>\n\n\n\nIn this release, Claude Agent is now available natively inside the JetBrains AI Assistant chat interface! Agents have full access to IDE capabilities via the JetBrains MCP server.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/12\/WS253_AIA_junie.png\")
<\/figure>\n\n\n\nNew default look: The Islands theme<\/strong><\/h3>\n\n\n\nThe Islands<\/em> theme is now the default look in WebStorm and other JetBrains IDEs. Designed to help you stay focused and code with ease, it features instantly recognizable tabs, enhanced in-editor contrast, distinct separation between work areas, and rounded corners. This update is purely visual, so all functionality remains unchanged.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/12\/image-6.png\")
<\/figure>\n\n\n\nDebugging JavaScript projects in remote environments<\/strong><\/h3>\n\n\n\nYou can now use WebStorm\u2019s built-in JavaScript debugger when developing remotely with WSL, Docker, or other remote setups. <\/p>\n\n\n\n
For frontend projects, the IDE launches a browser on your client machine that connects back to the remote environment, allowing you to set breakpoints and step through your code with the same workflow you use locally. WebStorm 2025.3 includes support for JavaScript debug and npm run configurations. We\u2019re actively gathering feedback to guide further improvements.<\/p>\n\n\n\n
Angular<\/strong><\/h3>\n\n\n\n\n- Angular 20.2
as<\/code> aliases in else if<\/code> blocks<\/strong> \u2013 WebStorm now understands<\/a> the new syntax introduced in Angular 20.2, allowing aliases in @else if<\/code> conditions. Available in WebStorm 2025.3, this fix will also be backported to 2025.2.3.<\/li>\n\n\n\n- Support for Angular 20.1\u2019s<\/strong> binary assignment operators <\/strong>(
+= <\/code>and -=<\/code>) in template bindings is now available in WebStorm 2025.2.1 and 2025.3 (WEB\u201173861<\/a>).<\/li>\n<\/ul>\n\n\n\nVue<\/strong><\/h3>\n\n\n\n\n- Initial Vapor mode support<\/strong> \u2013 Vue 3.6 introduced Vapor mode, a lightweight compiler that eliminates the runtime. WebStorm 2025.3 adds initial support for this, including:\n
\n- Recognition of the new
createVaporApp<\/code> factory function \u2013 directives registered in the application are treated as Vapor directives.<\/li>\n\n\n\n- The New Vue Component<\/em> wizard can now generate Vapor components that use either
<script vapor><\/code> or <script setup vapor><\/code>.<\/li>\n\n\n\n- Directives declared in a component\u2019s
script<\/code> section or registered via an application or plugin are recognised \u2013 global directives are partially supported.
<\/li>\n<\/ul>\n<\/li>\n\n\n\n- Composition and two\u2011script blocks<\/strong> \u2013 WebStorm now supports <\/a>multiple
<script><\/code> blocks in single file components.
<\/li>\n\n\n\n- Plugin\u2011registered directives<\/strong> \u2013 Vue 3 directives registered through plugins are now recognized. WebStorm 2025.3 adds support for both plugin forms (function and object with
install<\/code>). Directives are collected when the plugin is registered using app.use(myPluginWithDirectives)<\/code>, but not when the plugin is invoked as a function (WEB-52800<\/a>).
<\/li>\n\n\n\n- Global components and global directives<\/strong> \u2013 We\u2019ve fixed the issue where global components declared in the
GlobalComponents<\/code> interface were not resolved. Our fix<\/a> adds support for .d.ts<\/code> files in the types<\/code> field of compilerOptions<\/code> and makes the .d.ts<\/code> extension optional. Additionally, WebStorm 2025.3 implements support for the GlobalDirectives<\/code> interface, for example, Vuetify\u2019s vVuetifyClickOutside<\/code>.
<\/li>\n<\/ul>\n\n\n\nCSS<\/strong><\/h3>\n\n\n\nWebStorm 2025.3 includes a major CSS syntax data update based on synchronization with WebRef. This generic solution<\/a> brings the latest specification data into the IDE, ensuring modern and accurate CSS support.<\/p>\n\n\n\nThis includes support for math functions round()<\/code>, rem()<\/code>, and mod()<\/code>, as well as color-related features like color()<\/code>, conic-gradient()<\/code>, and others. If you encounter issues or have suggestions, please comment on the umbrella issue<\/a>.<\/p>\n\n\n\nVitest<\/strong><\/h3>\n\n\n\nVitest 4 introduced breaking changes to its reporter API, which previously caused WebStorm to show No tests found<\/em> errors for Vitest 4 suites. The integration has been updated to work with the new API and is available<\/a> in the 2025.3 release.<\/p>\n\n\n\nAstro<\/strong><\/h3>\n\n\n\nFixes to the Astro parser remove false errors when using expressions inside HTML tags and eliminate incorrect highlighting of truthy tags (WEB-60565<\/a>, WEB-69032<\/a>). <\/p>\n\n\n\nThese changes make Astro templates behave correctly in the IDE. In parallel, the team is working on a broader update to align WebStorm\u2019s Astro support with the official Astro Language Server for even better compatibility in a future release.
<\/p>\n\n\n\n
Prettier<\/strong><\/h3>\n\n\n\nThe new Prettier language status widget<\/strong> indicates whether the current file is handled by Prettier, displays any formatting errors on save, and provides a Go to Configuration File<\/em> action for quick access to your .prettierrc<\/code> or equivalent configuration files.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/12\/prettier_language_status_widget.png\")
<\/figure>\n\n\n\nWebStorm can now automatically run<\/a> Prettier when you paste code, ensuring that pasted snippets immediately conform to your project\u2019s Prettier configuration. You can enable or disable this behaviour in the Code Style <\/em>settings.<\/p>\n\n\n\nUnified <\/strong>JavaScript Runtime<\/em><\/strong> settings page<\/strong><\/h3>\n\n\n\nWebStorm 2025.3 introduces a unified JavaScript Runtime<\/em> settings page<\/strong> that consolidates Node.js, Bun, and Deno configuration. From this single page, you can configure interpreters for all supported runtimes and select the appropriate one for .js<\/code> or .ts<\/code> run configurations. Please keep in mind that Node.js is still used for the TypeScript and language servers (WEB\u201173571<\/a>).<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/12\/unified_javascript_runtime_settings.png\")
<\/figure>\n\n\n\nIf you\u2019d like a list of everything included in WebStorm 2025.3<\/a>, please check out the release notes<\/a>. As always, please share your feedback with us and report any issues you find to our issue tracker<\/a>.<\/p>\n\n\n\nThe WebStorm team<\/em><\/p>\n","protected":false},"author":1474,"featured_media":664513,"comment_status":"closed","ping_status":"closed","template":"","categories":[89,907],"tags":[8981],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/webstorm\/664279"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/webstorm"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/types\/webstorm"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/users\/1474"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/comments?post=664279"}],"version-history":[{"count":10,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/webstorm\/664279\/revisions"}],"predecessor-version":[{"id":684274,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/webstorm\/664279\/revisions\/684274"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/media\/664513"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/media?parent=664279"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/categories?post=664279"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/tags?post=664279"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ja\/wp-json\/wp\/v2\/cross-post-tag?post=664279"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}