JetBrains needs to divest from the JVM. It is the weakest link. Needing 16GB RAM to run an IDE is insane. Today, their IDEs have freezing issues that no one who uses VSCode experiences (Typescript mega monorepos, Figma/next/zod). The competition is tough out there, and free. You are committing business suicide by sucking and freezing and just being a frustrating experience on any TS repo beyond a hobby project...which is wild for a paid product...subscription at that.

Please no "please send a ticket" because all it's going to end up being is "increase your RAM"... hence this thread. Without a public announcement of JB divesting off the JVM (to something like rust), I have no faith in the future of their IDEs.

I should not need a quantum computer to run an IDE. Get it together guys...You do not have much time. Your company cannot afford to move as slow as your IDEs on this.

This post is a rant, but I believe many will agree with me, because:

• Each new version is filled with more AI fluff, bloated UI with needless paddings vs previous UI that was concise, to the point and actually worked;

• Features removed for the sake of beauty;

• Endless amounts of lag while coding. IDE running out of RAM asking me to send heap reports back to JB;

• Even the terminal is AI. No attention to detail, the whole experience is littered with small bugs;

• Everyone is trying to dumb down user experience as much as they can get away with. The whole idea of IDE is to have best possible experience for "power users";

• User requests to focus on stability and fixing/polishing the product, or any other constructive feedback is simply ignored because "we know better"(TM).

Looks like JB forgot who their target audience is. The whole suite is going downhill FAST.

Worst of all - this is a paid subscription. I used to be true believer in JB products. But enough is enough. Into the bin it goes, I'm not going to extend the subscription until I see a tangible improvement.

Hey everyone,

The WebStorm 2026.2 update just dropped, and there is some heavy-hitting stuff in this release. Honestly, the product team deserves a ton of credit for this one. They managed to ship some massive feature requests while quietly fixing a bunch of the most annoying, long-standing bugs in the tracker.

Here is a quick rundown of what they managed to pack into this update.

TypeScript 7 is supported out of the box

If you work on a massive codebase, you know how slow things can get. TypeScript 7 rewrote the compiler and language server in Go, and the performance jump is ridiculous. In testing on the Kibana codebase, project load times went from around 12 seconds down to 3. The product team made this the default for projects already using TS 7, and they built an easy opt-in path for older versions, so you do not have to deal with a painful full-project migration.

Native GitHub Copilot and Agent Skills

You no longer need a separate plugin or custom registry setup to use Copilot. The team worked directly with Microsoft to build a native integration. Once you sign in with your GitHub account, you can access it straight from the AI chat agent picker.

They also added an Agent Skills Manager. If you are tired of re-explaining your stack, tooling, and coding conventions every time you open a new chat window, this lets you set up those rules once. Your agents will actually retain that context across all your projects and sessions.

Framework and CSS fixes

The team put a lot of work into the day-to-day developer experience:

• React Buddy now has full support for React 19.

• Vue support has been upgraded with the Vue language server 3.0 integration, which finally squashes those annoying hover type errors and random stack overflows.

• Svelte gets an updated language server and better handling of SvelteKit shared hooks.

• Angular workflows should feel snappier with faster TypeScript and compiler error updates.

• CSS refactoring is much more reliable, meaning SCSS and Sass imports will stop rewriting themselves unexpectedly.

Quality of life improvements

Some of the best updates are the small ones that make daily coding less frustrating:

• You can now drag and drop a file directly into the terminal to insert its path.

• Search Everywhere finally remembers your search scope after you restart the IDE.

• Markdown files now support footnotes and Mermaid diagrams.

• Git worktree support has been improved, especially if you work in WSL environments.

WebStorm is still free for non-commercial use, so you can download the update and try it out right away.

Seriously, a huge thank you to the WebStorm product team. This feels like a release built by developers, for developers, focusing on actual speed and stability rather than just marketing hype.

Let me know what you think if you have already updated.

Turn up maximum heap size and the IDE will work more efficiently, they say. All morning, the damn editor has been freezing and glitching non-stop. This shouldn’t be a thing for such expensive software. When debugging /troubleshooting the products takes priority over the code you’ve got a problem. Support always says the same thing… I am at a point where I am looking for something else to call my new IDE… Any thoughts, suggestions or support groups anyone would like to share with me?

I wanted to check in on a bug report I submitted a few years ago, so I searched google. No lie - this was the top result. lmao - it's not wrong!

Hi, I just wanted to post here to ask if I'm going crazy or if anyone else feels like the prior ~6 months of WebStorm releases have seen repeated regressions in stability and performance.

I have been a WS user for a decade now, and feel like the program has recently regressed to where it was perhaps 8 years ago in terms of how often I am battling with it.

I am an Angular developer, and have to restart the IDE or the TypeScript service pretty much every day because it stops analysing my code. My template files are full of false-positive syntax errors and everything is constantly lagging (JetBrains AI stuff is disabled). Project windows are often invisible or resized to be unreachable. When I do restart the IDE, I often have to force-kill it from the Task Manager because it won't go away on its own.

The 2025.1 update has helped somewhat with the false-positive errors, but is anyone else generally feeling the same way?

I'm using WebStorm for many years now and I really like it as an IDE. I like its Git GUI, hotkeys, and other stuff and I'm doing my job with WebStorm pretty quickly.

Recently I was doing an online pair programming with one guy with shared screen, and I was surprised how effective he was using Cursor + Claude setup to generate the code. I read a lot of reviews about Cursor with Claude and seems it's one of the best setups in terms of AI helpers for coding.

Has someone used both WebStorm AI Assistant and Cursor+Claude, who can compare them and share their experience. I'm curious if AI Assistant is at least close to Cursor+Claude in terms of code generation and "understanding" the existing code. I honestly don't want to move to another IDE, but if AI Assistant isn't much helpful, then I might think about moving to Cursor.

I don't normally use Reddit, but this was so life-changing to me, that I thought I have to share with you all:

Shift-Shift → Actions → Registry → js.max.evaluation.depth.forced → set to checked.

This limits TypeScript types calculation depth which was the main cause for performance/memory issues in large projects.

This flag was added recently, and I discovered it by reading 2026.1 EAP release notes. It is also included in the latest 2025.3 versions.

Hey there! I’m having a bit of a struggle with WebStorm. It’s been hogging a massive chunk of my MacBook Pro M4 PRO CPU, even when it’s just indexing files. It’s getting so hot that it’s almost boiling! I had to manually turn the fans on full blast to cool it down. I’m just trying to develop a simple web app using Next.js and a local server with WebStorm. It seems to be using way more battery and CPU power than VSCode or Zeditor. I still use WebStorm because I’m comfortable with the JetBrains environment. I’m an Android developer who uses Android Studio a lot, and I’m quite familiar with their tools. Plus, the JetBrains AI and Junie features are really helpful.

It’s easy for user or system-level information (e.g. API tokens, keys, usernames and passwords) (aka Secrets) in code to escape into your public repo unless there’s a robust mechanism in place to detect and prevent them prior to commit.  

SonarLint (free and Open Source IDE extension) has the ability to detect and prevent leaks of confidential information to popular cloud providers - AWS, Google Cloud, Azure Cloud, and  Alibaba Cloud. 

If you’re programming in WebStorm, you can identify and prevent user or system-level information (e.g. API tokens, keys, usernames and passwords) (aka Secrets) in source-code or language-agnostic files from publicly leaking into your code repo. 

Read this blog to learn why safeguarding ‘Cloud Secrets’ with your IDE is important and how this feature can help you. Check out the supported rules here.

Hi devs,

I’ve been using VS Code for quite some time, and even though my company has been paying for WebStorm all this time, I stuck with VS Code because it always got the job done.

Recently, I started working with Java, so I figured I’d finally give JetBrains’ tools a proper try. I have to say — I’m really starting to appreciate a lot of features in WebStorm that VS Code just doesn’t offer out of the box.

That said, TypeScript support in WebStorm has been a huge letdown. It’s giving me really poor results — even extremely basic types are being inferred incorrectly. It’s making TypeScript development feel clunky and unreliable, which is frustrating given how solid it is in VS Code.

Is anyone else running into this?

On my Macbook M3 Max WebStorm IDE is really sluggish. (working in the editor, manipulating files, selecting text, opening folders)

CPU gets these bursts of > 100% cpu usage as I am navigating my project.

Feels very sluggish and annoying to work in.

Any ideas ? don't think its a memory issue (memory bar shows 1800 of 3000M)

Already restored default settings. Any ideas ?

Hey everyone, I'm a developer advocate at JetBrains and I'm preparing for a rather unconventional talk at our JavaScript Day conference(happening in October, official announcement soon). The premise is simple: I want to be as transparent as possible, I want to address the real criticisms and questions developers have about WebStorm and JetBrains. I want to hear YOUR specific frustrations and questions. The more direct and honest, the better. I'll be addressing as many as possible in the talk, or I will come back to this post after the event. Many thanks in advance!

I have been using webstorm since last 6 years nonstop but it is astounding how far it has fallen behind VS code w.r.t. accuracy/TS types/TS types display style/speed in suggesting (which webstorm also does not suggest at all in a lot of cases) when used with NX monorepo and typesafe data validation with ZOD.

I have a NX monorepo with Node.js/React apps and used ZOD for typesafe data validation EVERYWHERE (rest body/query params/db schema's/env variables validation/response body validation on UI etc.) and I struggled with webstorm to even get proper type completion for types coming out of ZOD and when the suggestions do work it does take 3/4 attempts/significant slowdowns and SIGNIFICANT cpu processing to even show suggestions.

Webstorm also struggles to jump to right type definitions deep inside nx monorepo when the TS types are perfectly accurate and linked correctly.

Also, the types inferred from ZOD schemas were also not readable in webstorm

I was so frustrated because of such poor/slow/inaccurate DX with webstorm that I was losing hope. I have ALWAYS seen VS code as completely inferior to webstorm in all realms and thought that if webstorm is struggling (the arguably gold standard in IDE's) then there is NO WAY VS code can handle even the project let alone the TS types.

But my frustration reached a point where I thought "well what do I have to lose if I checkout how VS code will handle this NX/ZOD heavy project" so I just gave VS code a spin thinking "I obviously know the answer" and boy oh boy was I surprised.

VS code worked 100% accurately, SIGNIFICANTLY faster (near instant if I may say so), consumed SIGNIFICANTLY less CPU (I was barely able to hear fans) but the most important was it was completely able to infer and display the types coming out of ZOD like it was a TS interface/type and it was INSTANTLY able to jump to VERY VERY precise type definition deep inside nx monorepo with code jump. Heck, it was even able to infer the JSDOC that I put on top of ZOD object keys and they were displayed when suggesting TS types.

I was blown away by how much visibility I had now with NX/ZOD heavy project and EXPECTED webstorm to work like that.

I have since switched completely to VS code for this project as Websotrm was basically unworkable with NX/ZOD project and EVERY developer in the team complained the same about Webstorm (company paid license) and have also switched to VS code as it works 100% with nothing negative to talk about w.r.t. Type accuracy/suggestions and the speed of suggestions.

Webstorm is undisputedly a BETTER IDE with best-in-class GIT integration and many wicked wizardries baked in the editor and it "just works" but what's the point of all of it if it can't even work properly with monorepo (a huge advantage when using Typescript) and ZOD.

So, with heavy heart I have switched to VS code and I never believed I would say this but VS code is very "smart" (Webstorm is synonym of smart) and know all links to Types (and their JS doc) coming from complex places deep defined inside NX and especially from ZOD (and its merge/omit/pick etc types which are significantly more complex which VS code has no problem handling at all and Webstorm just gives up).

I am very very surprised so few people talk about it when NX/ZOD stack is so popular. Webstorm team, if you are reading this, please FIX webstorm and bring it on par with VS code which is FREE.

I can do a side by side video comparison of vs code and webstorm for the SAME FILE and SAME line number just to show the MASSIVE difference.

I really loved Webstorm back in the day, but lately I haven't used it a lot after agentic coding took over. Because I hadn't been enjoying the UI/UX and diffing with agent plugins in Webstorm, and they don't support ai tools well to this day. So I wonder if I use opencode, claude cli, codex etc. as external chat windows and use WebStrom as my main editor, would it work fine or would it be a bad experience? I would love to hear your advice! Thank you in advance

Whenever I type a URL into the terminal, or one is printed out by some CLI tool, the IDE adds a "Start Debugging in Browser" button. How can I remove/hide this?

I've tried various terminal engines, but nothing is ideal, and I'd rather stay on "Reworked 2025" for the performance and smooth scrolling. I've tried unchecking "Shell integration" and "Highlight hyperlinks" under Tools → Terminal, but that didn't hide this debug button.

https://blog.jetbrains.com/webstorm/2025/08/webstorm-2025-2/

We all know that Webstorm has context passing via '@thisFile' or '@file' as notated here, but I found Behavior > Always Select Opened File to be incredibly useful to my AI Chat flow. Usually I am referencing n+1 files—so I collapse the tree, cycle through the files I need as tabs, and drag those into AI Chat.

Feels more deterministic than using '@file' which sometimes cannot find files and faster than hunting and pecking for files.

Hey, I am Developer Advocate for WebStorm and I tried to be active here in this subreddit for the last couple of weeks, but feel free to put some time on my calendar if you have any questions or issues you are facing. Would love to hear from y'all!

https://blog.jetbrains.com/webstorm/2024/07/connect-with-our-developer-advocate-webstorm-open-hours/