DOWNLOAD WEBSTORM 2025.1 BETA<\/a><\/p>\n\n\n Important! WebStorm Beta builds are not fully tested and might be unstable.<\/strong> Please try the latest build and share your feedback with us. You can do so using our issue tracker<\/a> or by leaving a comment on this blog post.<\/p>\n\n\n\n JetBrains AI Assistant is advancing its line of models! We\u2019ve added support for Claude 3.5 Sonnet and Claude 3.5 Haiku, now provisioned in Amazon Bedrock. This means you\u2019ll benefit from sharper responses, faster insights, and an even smoother experience. AI Assistant\u2019s lineup of OpenAI models now includes o1, o1-mini, and o3-mini.<\/p>\n\n\n\n Update<\/strong>: A new version of the JetBrains AI Assistant plugin<\/a> has been released, bringing support for even more models, including: In addition to cloud-based models, you can now connect the AI chat to local models available through Ollama and LM Studio! You can set up local providers via Settings<\/em> | Tools<\/em> | AI Assistant<\/em> | Custom Models:<\/em><\/p>\n\n\n\n For the 2025.1 release we have focused on improving AI-based completion in the context of web framework components. These changes affect local full line code completion as well as cloud-based completion suggestions:<\/p>\n\n\n\n AI-powered test generation now offers more careful framework detection, especially for cases when multiple frameworks are present. Additionally, generated tests respect naming conventions:<\/p>\n\n\n\n The engine previously known as WebStorm@next or the Use types from server<\/em> option now has an official name \u2013 the service-powered type engine<\/a>! We’re currently polishing it, with a focus on performance. A dedicated icon in the status bar displays the engine’s status, and you can granularly enable or disable it for supported frameworks or for TypeScript in general within the current project:<\/p>\n\n\n\n If you notice any degradations when the new engine is enabled, please use the Submit a bug report<\/em> link.<\/p>\n\n\n\n WebStorm now supports code completion for host binding attributes based on directive selectors. Quick-fixes for creating fields are also available within binding expressions. Moreover, refactoring is supported across different locations and is even available for CSS classes:<\/p>\n\n\n\n The long-awaited support for Reactive Forms is here. This update includes code completion, syntax highlighting, validation, refactoring, and quick-fixes for Reactive Forms. Both declaration styles \u2013 constructor-based and builder-based \u2013 are fully supported.<\/p>\n\n\n\n There is also a new intention to extract or inline component templates. Invoke Show Context Actions<\/em> (\u2325\u23ce <\/em>(macOS) \/ Alt+Enter<\/em> (Windows\/Linux)) to use the action:<\/p>\n\n\n\n This release brings many other improvements and bug fixes for Angular beyond the features mentioned above.<\/p>\n\n\n\n WebStorm 2025.1 Beta introduces automatic run configuration creation for Next.js applications. Now, you can easily initiate debug sessions for both the client and server components of your Next.js application using the Run widget<\/em>.<\/p>\n\n\n\n The New Project<\/em> wizard now gives you the option to generate a new Nuxt project using the Nuxt CLI ( We\u2019ve also implemented several bug fixes, including:<\/p>\n\n\n\n In WebStorm 2025.1 Beta, invoking Show Context Actions<\/em> (\u2325\u23ce (macOS) \/ Alt+Enter (Windows\/Linux)) now opens the floating toolbar with different action groups. The toolbar also appears when you select code in the editor:<\/p>\n\n\n\n The floating toolbar contains the following actions and action groups:<\/p>\n\n\n\n You can customize the contents of the toolbar by opening the kebab menu (three vertical dots) and selecting the Customize Toolbar\u2026<\/em> option<\/p>\n\n\n\n Creating new files is now easier in the Project <\/em>tool window. You can simply use the + icon located directly in the window\u2019s toolbar:<\/p>\n\n\n\n WebStorm 2025.1 Beta introduces the following improvements for Prisma:<\/p>\n\n\n\n <\/p>\n\n\n\n WebStorm now automatically detects and applies the nearest in the directory tree Prettier configuration when formatting files, ensuring the code style is consistent across subprojects. The Indentation status bar widget shows whether Prettier has modified the code style. The new dropdown menu offers the following options:<\/p>\n\n\n\n Code style changes made by Prettier are visible in the Code Style<\/em> tab under Settings<\/em>, where you can also disable automatic modifications.<\/p>\n\n\n\n A new setting controls whether WebStorm should use Prettier to auto-format code styles. This option is enabled by default. In case if We are consistently working to improve reliability and performance in mono-repo setups. Here are some of the most noticable fixes in this build for long-standing issues:<\/p>\n\n\n\n That\u2019s it for today. For the full list of improvements introduced throughout the latest 2025.1 EAPs, check out the release notes.<\/p>\n\n\n\n The WebStorm team<\/em><\/p>\n","protected":false},"author":1474,"featured_media":552808,"comment_status":"closed","ping_status":"closed","template":"","categories":[826,89],"tags":[8721],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/webstorm\/552606"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/webstorm"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/types\/webstorm"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/users\/1474"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/comments?post=552606"}],"version-history":[{"count":10,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/webstorm\/552606\/revisions"}],"predecessor-version":[{"id":561764,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/webstorm\/552606\/revisions\/561764"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/media\/552808"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/media?parent=552606"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/categories?post=552606"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/tags?post=552606"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/cross-post-tag?post=552606"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Key improvements<\/h2>\n\n\n\n
AI Assistant<\/h3>\n\n\n\n
\u0421laude and local LLMs<\/h4>\n\n\n\n
\n
\u2022 Claude 3.7 Sonnet
\u2022 OpenAI GPT-4.5
\u2022 Gemini 2.0 Flash<\/p>\n<\/blockquote>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-ai-models.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-local-llms.png\")
<\/figure>\n\n\n\nImproved AI completion for web frameworks<\/h4>\n\n\n\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-ai-completion-1.png\")
<\/figure>\n\n\n\nEnhanced AI test generation<\/h4>\n\n\n\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-AI-test-gen.gif\")
<\/figure>\n\n\n\nTypeScript<\/h3>\n\n\n\n
Service-powered type engine<\/h4>\n\n\n\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-TypeEngine.png\")
<\/figure>\n\n\n\nAngular improvements<\/h3>\n\n\n\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-Angular-host-binding.gif\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-reactive-forms.gif\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-Angular-templates.gif\")
<\/figure>\n\n\n\nNext.js improvements<\/h3>\n\n\n\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-NextJS-debug-1.png\")
<\/figure>\n\n\n\nVue improvements<\/h3>\n\n\n\n
nuxi<\/code>):<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-Nuxt.png\")
<\/figure>\n\n\n\n\n
vue<\/code> are now resolved.<\/li>\n\n\n\n__VLS_WithTemplateSlots<\/code>.<\/li>\n<\/ul>\n\n\n\nUser experience<\/h3>\n\n\n\n
Floating toolbar<\/h4>\n\n\n\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-floaing-toolbar.png\")
<\/figure>\n\n\n\n\n
New file creation in the Project tool window<\/h4>\n\n\n\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-new-file-from-project-view.png\")
<\/figure>\n\n\n\nGraphQL and Prisma<\/h3>\n\n\n\n
\n
gql(query)<\/code> syntax support (WEB-71611<\/a>)<\/li>\n<\/ul>\n\n\n\nPrettier integration improvements<\/h3>\n\n\n\n
\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-prettoer-widget.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2025\/03\/WS251-Prettier-settings.png\")
<\/figure>\n\n\n\n.editorconfig<\/code> is present, Prettier takes precedence for files it handles, but if certain options aren\u2019t specified in Prettier, EditorConfig settings still apply.<\/p>\n\n\n\nMonorepo support<\/h3>\n\n\n\n
\n
package.json<\/code> export fields are now processed properly.<\/li>\n\n\n\npackage.json<\/code> exports are now used by auto-import in monorepos.<\/li>\n<\/ul>\n\n\n\n