WebStorm 2026.1 Is Out — Let's Break It Down Live
In a Nutshell
WebStorm 2026.1 shifts to the official TypeScript language service as the default engine, replacing their custom Kotlin implementation to achieve guaranteed type accuracy and better performance on large projects. Framework support improved across React 19 directives, Angular templates, Vue type checking in templates, Svelte 5 generics, and Astro language server integration. New AI capabilities include Next Edit Suggestions, an experimental features plugin with Recap/Insights/Group, and upcoming Skills registry for consistent agent configuration.
These notes were generated by AI and may contain inaccuracies.
Jason Torres and Denny Kost introduced themselves as the new developer advocates for WebStorm and JavaScript tooling at JetBrains. The release of WebStorm 2026.1 was delayed due to technical issues but expected to be available within minutes to days.
The stream is being recorded and will be available on YouTube. Viewers can pause and return later. Questions can be submitted through the YouTube chat and will be addressed during the session.
The primary focus of the update centers on handling TypeScript at scale as projects grow larger and more modular. The IDE needs to maintain accuracy and performance with larger codebases.
The service-powered TypeScript engine is now enabled by default. WebStorm now relies directly on the official TypeScript language service rather than maintaining a separate Kotlin-based type engine. This provides more accurate type inference, lower CPU usage on larger projects, and ensures IDE behavior matches actual build output.
The team previously built their own type engine in Kotlin to achieve fast type inference, similar to the TypeScript team's approach of moving to Go. However, achieving 100% correctness proved challenging, particularly with the final 5% of edge cases. The decision was made to abandon the custom approach in favor of using the official TypeScript language server for guaranteed correctness.
For TypeScript files and React projects with TSX, the service-powered type engine provides proper type inference. Support for Angular and Vue frameworks with specialized TypeScript flavors is still being evaluated. Angular support is currently in beta and expected to become default in a future minor release. Vue requires additional work due to its unique TypeScript implementation.
Map types with template literal keys are now fully resolved. Previously, complex generics like get name, get age, get email would produce "any" types, but these are now correctly typed.
TypeScript 6 no longer auto-includes every package from node_modules, and WebStorm now reflects this behavior to match TypeScript's actual inclusion logic. TypeScript 6 is moving toward explicit paths and mapping, which WebStorm now follows to ensure IDE and TypeScript agreement.
Memory consumption should remain stable in normal operation. Memory issues typically stem from memory leaks or project-specific conditions involving plugins and other factors. Users experiencing memory problems should create a ticket and share logs collected via Help → Collect Logs and Diagnostic Data. This provides plugin information, stack traces, and diagnostic details necessary for troubleshooting.
While JetBrains IDEs consume more memory to provide additional flexibility, the goal is consistent memory usage rather than unexpected spikes.
String literal named exports represent a newer TypeScript feature allowing function exports with string names. Previously, WebStorm treated these strings as arbitrary text with no navigation, rename, or type resolution support. Full IDE support including cross-file rename refactoring is now available, making this feature practical for real codebases.
Preparations are underway for TypeScript 7, which will use TypeScript Go. Official claims indicate 10x faster performance and 6-7x less memory usage compared to the current TypeScript language server. While not a one-to-one mapping, noticeable speed and memory consumption improvements are expected.
AI features operate outside the IDE release cycle through plugin updates. Several new agents were added at the beginning of the year, including Codex, which is used for approximately 90% of development work. The team maintains up-to-date model availability, including GPT 5.4 mini released the previous Monday.
The Agent Client Protocol (ACP) enables "bring your own agent" functionality, allowing users to connect preferred agents through a standardized interface. This provides automatic updates and access to agents like Open Co 2, Pi, and the Cursor agent, including proprietary models like Composer 2.
Cloud Code's Cloud agent is being migrated to ACP for consistent user experience, providing access to models like Opus 4.6 and installed skills from Cloud Code.
Playwright support exists through the test automation plugin, which originated from the discontinued Aqua QA IDE. Basic Playwright support for run and debug operations should be available, though the recorder feature is not included. A community plugin may provide recording functionality.
JetBrains plugins typically work across IDEs, with occasional feature experimentation beginning in IntelliJ IDEA before broader rollout. Additional context was requested regarding the specific workspaces plugin mentioned.
Next edit suggestions (ghost text) became generally available around Christmas and expanded beyond JavaScript, Java, TypeScript, and Python to other languages. Integration with refactorings allows automatic updates to related locations, making quick fixes more accessible for parameters and functions.
A separate experimental features plugin called "IntelliJ AI Assistant Experience" provides access to more invasive workflow features requiring explicit user consent. Three features are available:
- Recap: Summarizes recent actions to help users resume work after interruptions like meetings or production incidents
- Insights: Automatically identifies complex functions and generates explanatory code comments to reduce cognitive load
- Group with AI: Organizes local changes by semantic groups rather than file-by-file, prioritizing based on criticality for more efficient code review
React 19 with the React compiler introduced file-level directives use client and use server. Two additional directives were added: use memo and use no memo.
use no memo prevents memoization for components requiring fresh re-renders with live data, such as real-time data feeds where stale caching would cause bugs.
use memo enables automatic memoization for static content like product lists without real-time updates.
WebStorm provides syntax highlighting and consistent visual treatment for all four directives (use client, use server, use memo, use no memo), enabling quick visual scanning of compiler opt-ins across large codebases.
TypeScript Go improvements will provide speed and memory benefits, though memory leak root causes remain unchanged. Users experiencing memory issues should still file tickets for investigation rather than relying solely on language server improvements.
Support for cursor-like features where pressing tab automatically jumps to the next file about to be modified is partially available through IDE actions. Multi-file edit is not yet available but remains in development. Experiments with ACP are underway to potentially get next edit suggestions from different providers. This would provide an alternative if users prefer different behavior from JetBrains AI next edit suggestions or tab completion.
Angular template type checking is handled using parts of the Angular language server as preparation for the new TypeScript engine and TypeScript Go. Angular remains part of the service-powered type engine due to these ongoing preparations. The service-powered type engine with Angular yields better results when heavily using signals, though it remains in beta with some rough edges expected to stabilize in the 2026.1 minor release.
Support was added for new template functions including regex in templates. Inline arrow functions are now supported, allowing functions to be passed as references to components. The IDE provides warnings when syntax expectations differ from actual implementation, showing normal TypeScript syntax highlighting for inline functions supported in Angular 21.
Spread syntax in templates is now supported, enabling sharing of styling and passing properties to generic components. IDE support includes proper handling of this syntax, which provides a declarative approach that keeps component classes slimmer.
Single file components have three blocks: script, template, and style. TypeScript in the script setup block has always worked well, but the template was problematic with inconsistent type inference, broken auto-complete, and errors that wouldn't surface until runtime. The 2026.1 release ships updates that carry prop definitions from the script block into the template layer, enabling literal union types to resolve inside templates.
Type errors are now caught inline in the template before running anything. This includes component prop checking that shows type mismatches, such as expecting a boolean but receiving a string. The same prop-level type checking expected in JavaScript is now available in Vue templates.
The Vue language server has support for some features but may lack the ergonomics desired for IDEs, particularly with embedded languages like CSS in HTML. Refactorings and user expectations are not met by language servers alone. A compromise approach is needed to determine where to use custom implementations versus language servers, especially for templates mixing HTML, CSS, and TypeScript with type checking.
Astro support had a chicken-and-egg problem where initial implementation wasn't sufficient to justify full IDE experience investment. The decision was made to get closer to the Astro language server for technically correct experience. Improvements include proper navigation to Astro components, proper auto-complete, and better handling of Astro's mix of markdown and JSX. Language server configuration overrides are now available for special setups.
AI context is limited to project scope. Breaking the project concept to go outside the workspace would require clear user experience design. Agents that can navigate everywhere from a starting point give up developer control, which needs proper UX consideration. Nested workspaces with several projects in the same folder hierarchy should work technically.
Svelte 5 introduced generic components through the generics attribute on the script tag, allowing components to be typed over type parameters like generic functions. This pattern is powerful for reusable tables, lists, and selects where consumers need type safety. Before 2026.1, WebStorm saw generics but couldn't navigate them, rename them, or find usages, treating TypeScript generics like regular text.
Full navigation now works for generic type parameters, highlighting all usages and jumping to declarations in generic attributes. Rename functionality works across script blocks, prop interfaces, and templates with consistent changes. Find usages shows all references of type parameters. The IDE understands that generics require TypeScript, providing notifications when the attribute is missing.
Git UI is handled by the PhpStorm team with improvements for work trees planned or landed in 2026.1. Specific details require direct outreach for clarification on requested improvements.
Skills allow adding knowledge to agents or shaping prompts in ways that are tedious to do manually or spread knowledge across teams through conventions. Current configuration differs between tools like Cloud Code, CodeX, and Juni, creating inconsistent experiences. A new skills registry in AI Assistant settings allows installing skills for codebases, making the experience more pleasant. Skills are exposed to agents through commands like /front-end skill. This feature is not in 2026.1 but expected soon, potentially within the next week or two.
A raffle for WebStorm licenses is running where participants put their favorite WebStorm feature in the video comments. Winners will be contacted next Friday to receive licenses that can be given to friends, colleagues, or others. WebStorm 2026.1 has a deployment issue with Linux registry snap preventing immediate release, though it should be available soon through blog posts and regular news channels.
Keep JetBrains in your library
Save the videos and channels worth coming back to, and find them again in one place.
