WebStorm, a JetBrains IDE

@WebStormIDE

The JavaScript and TypeScript IDE, by @JetBrains Tips and tricks: #WebStormTip New features: #NewInWebStorm

JetBrains s.r.o.

jetbrains.com/webstorm/

Joined March 2013

Pinned
WebStorm, a JetBrains IDE
@WebStormIDE
Jul 16
WebStorm 2026.2 is out! Large TypeScript codebase? This release has your back. TS 7 ships out of the box, no migration needed. We tested it on Kibana, and project load time went from ~12s to ~3s. What’s more, GitHub Copilot is now natively integrated (no plugin setup required),
WebStorm, a JetBrains IDE
@WebStormIDE
11h
Bring your own agent to WebStorm. GitHub Copilot, Claude Code, or any ACP-compliant agent – connect them directly, with no JetBrains AI subscription required. ACP handles the protocol. You pick the agent. Read more: jetbrains.blog/40dikk #WebStormTip
The "LSP Moment" for AI Agents: WebStorm ACP - The JetBrains Blog
From blog.jetbrains.com
WebStorm, a JetBrains IDE
@WebStormIDE
14h
Did you ever dream that your AI agent would be able to check its own work in the browser? Well, dreams do come true. Chrome DevTools Connect for WebStorm lets agents see and interact with the browser directly. It ships as a bundled Chrome DevTools CLI skill inside WebStorm, with
Chrome for Developers
@ChromiumDev
Aug 12
Meet Chrome DevTools Connect for WebStorm → goo.gle/4i2wPuL Now your AI agent can open Chrome, inspect rendering, read console logs, and verify runtime fixes without you leaving the WebStorm IDE.
00:00
WebStorm, a JetBrains IDE
@WebStormIDE
Aug 12
How do you evolve a language used by millions of developers without breaking the web? That's TC39's job – the committee that designs and evolves JavaScript. We sat down with TC39 committee members during their 114th meeting, hosted at JetBrains' office in Amsterdam, to talk
Inside TC39: Evolving JavaScript Without Breaking the Web
From youtube.com
WebStorm, a JetBrains IDE
@WebStormIDE
Aug 10
Chrome DevTools Connect for WebStorm is now live! The agent can now open Chrome, read console logs and network requests, take screenshots, and interact with the page. The agent reaches for the browser when it decides runtime verification is needed, or when you ask it to. It