Released: Aug 4, 2025

2025.2 での更新項目

機能

• TypeScript-Go language server experimental support - WebStorm 2025.2 introduces experimental support for the new TypeScript-Go language server, bringing improved performance and modern architecture for TypeScript development.
• Baseline support - WebStorm 2025.2 now displays Web Platform Baseline information directly in quick documentation. When you hover over a web platform API, you'll see details about when the feature became reliably available across major browsers, based on WebDX CG's Baseline data.
• Bun improvements - WebStorm 2025.2 introduces smarter integration for Bun. When a bun.lockb or bun.lock file is present in your project, WebStorm will automatically detect Bun and set it as the package manager. WebStorm will also create a Bun run/debug configuration when you try to run or debug a file by invoking it from the context menu. All relevant actions, such as running bun install, using context menu options for package.json, and resolving dependency suggestions, will default to Bun.
• AI
  • AI agent upgrades - Junie, the coding agent by JetBrains, is available for WebStorm users and has recently received several major updates to its functionality.
    • Now 30% faster.
    • MCP support is now available: The Model Context Protocol allows Junie to connect to external sources like databases, file systems, or APIs.
    • Remote development is now supported in Junie: You can work remotely with your team and delegate tasks to Junie at the same time.
  • AI Assistant improvements
    • Smarter completion across all supported languages, now with support for SQL, YAML, JSON, Markdown, and more.
    • JetBrains Al Assistant now supports image attachments in the chat when using Anthropic and OpenAl models.
    • Improved AI chat - In WebStorm 2025.2, AI Assistant now supports local code embeddings for JavaScript and TypeScript. This means it can analyze your codebase locally to provide more accurate, context-aware answers tailored to your project. The result is smarter, more relevant assistance when working in JavaScript and TypeScript codebases.
• Frameworks and technologies
  • Angular: Support for the in keyword in templates - Webstorm 2025.2 adds support for the in keyword in Angular templates - functionality that was introduced in Angular 20. You can now use expressions like foo in myObj and @if (key in myObj) directly in your templates with full code highlighting and validation.
  • Disabled built-in formatter when Prettier is used - Starting with WebStorm 2025.2, the built-in formatter is automatically disabled for full-file formatting if Prettier is configured in your project. This helps you avoid formatting conflicts and ensures consistent results across your codebase. On-the-fly formatting and other editor features still work as expected, but full-file formatting defers to Prettier when it's present.
  • Updated Prisma LSP - Version 2025.2 updates WebStorm's Prisma support to LSP version 6.10.1, bringing the IDE compatibility fixes and adjustments required by the latest changes in Prisma's language server. The update ensures continued stability, code insight, and formatting support when working with .prisma schema files.
  • Reworked GraphQL support - WebStorm 2025.2 introduces a reworked implementation of GraphQL language injections in TypeScript and JavaScript files. Autocompletion, symbol resolution, syntax highlighting, and documentation lookup now work more reliably for GraphQL queries inside template literals.
• UI / UX
  • Parameter Info popup improvements - WebStorm 2025.2 introduces several improvements that make the Parameter Info popup easier to read and navigate.
• Testing
  • Jest support improvements - This release has resolved several long-standing issues with Jest integration. Test suites that use jest-circus and fail during teardown are now correctly reported as failed. In addition, Jest tests are no longer mistakenly executed as Playwright tests in certain setups.
  • Vitest support improvements - WebStorm 2025.2 includes several fixes that improve the accuracy of test results when you're working with Vitest. Test trees are now displayed correctly, even when multiple suites share the same name. Additionally, test suites that fail in an afterAll hook are now properly marked as failed, ensuring results reflect the actual test outcomes.