WebStorm 2026.1 is now available! Here are the highlights:
- More reliable TypeScript experience with a service-powered TypeScript engine enabled by default
- Codex in the AI chat
- ACP Registry for quick access to more agents
- Next edit suggestions for smarter file-wide changes
@draylegend_ It would be very helpful if we could take a look at your logs. Could you please submit a new issue in https://t.co/n4CAY42too and attach your logs zipped via Help > Collect logs and diagnostic data?
@Yoganesh_ Hi! Please submit a new issue in https://t.co/n4CAY42too and attach your logs (Help > Collect logs and diagnostic data). The team will look into it. Thanks!
WebStorm 2026.1 is now available! Here are the highlights:
- More reliable TypeScript experience with a service-powered TypeScript engine enabled by default
- Codex in the AI chat
- ACP Registry for quick access to more agents
- Next edit suggestions for smarter file-wide changes
wow @WebStormIDE is 16 today 🎂
@jetbrains shipped 1.0 for a simple reason: developers were using their other IDEs just for HTML, CSS, and JS.
Happy #birthday to the tool I work on every day
whats your favorite feature? drop it below!
Today is the 15th Global Accessibility Awareness Day.
In honor of it, we want to share recent improvements to compatibility with assistive technologies across different platforms, keyboard navigation, and non-visual feedback in JetBrains IDEs.
Some of these improvements are already available, and some are coming later this year. Check out the thread for more information.
#GAAD
TypeScript 7 is dropping a new compiler written in Go. It's 10 times as fast as the current compiler, but there's a catch: it won’t support extension APIs at launch.
Instead of waiting around, WebStorm is building an open-source fork to serve as a day-one bridge for Angular, Vue, and React.
Here is the real plan – no PR, just the engineering reality.
TypeScript Go is coming. @typescript 7.0 ships with a Go-based compiler.
10x faster.
No extension APIs at launch.
Here's what @WebStormIDE is doing about it, the real plan, not the PR version.
Full thread 🧵👇
"Developers are figuring out how IDEs fit into a world where agents do half the coding – that content doesn't exist yet."
~ Tünde Varga
We heard you.
What happens when an agent sees a green checkmark, but WebStorm sees a dozen type gaps?
A text-search editor isn't enough. You need the semantic index. Because WebStorm understands the AST, it catches the hallucinations agents miss.
The IDE isn't where you write anymore. It's where the agent gets grounded.
Manual component extraction is about to get a whole lot smoother. We’re bringing the Extract Component to File refactoring to WebStorm 2026.1.1!
Soon, you can stop moving code by hand:
✅ Control + T to extract instantly
✅ Optimized for modern functional components
✅ Auto-inferred TypeScript types
Architecture is about to get a whole lot faster.
We asked. You answered.
Someone in our Discord mentioned that Call Hierarchy doesn't always hit the mark for React components. They were right—so we're showing you the intended pro path for React navigation.
Stop fighting the IDE and start using the shortcuts designed for your workflow:
✅ Cmd + B: Jump straight to component source.
✅ Cmd + Y: Reveal full type definitions (no more truncated hints).
Watch how to level up your React workflow in 60 seconds.
What should we cover next? Drop a comment below.
Junie CLI now connects directly to your JetBrains IDE.
The agent sees what you see. Builds what you build. Refactors with full semantic context.
Learn more: https://t.co/eRN56eBSlq