I use it every day for Javascript/Typescript and it works great. It's definitely not just for Java; many many languages are supported (https://www.jetbrains.com/ides/).

The bug you linked to seems rather esoteric (someone didn't want to manually type "import {blah} from package"...?). If you start to type that import, it'll autocomplete the rest for you. And once it's imported, it's very very good at traversing library files and types and bringing you to the definitions (VScode can do this too).

Does it have bugs? I'm sure. And it has its own absurd annoyances (like https://youtrack.jetbrains.com/issue/IJPL-60969/Show-path-in...) that might never get fixed. But in general it works great.

When you try import {blah} from package blah will not autocomplete. That is my point. Every other editor works in this case. And npm link is quite a common case.

Why don't they just add it to package.json? I don't understand why this is a big deal at all. It'd be weird to me if a repo started to use random libraries that I didn't explicitly add to its manifest, even if I npm linked them... but I guess that's just me?

If it's important to you, I guess this is not the right IDE for ya!

It is in package.json

What? The repro instructions say to leave it out.

Anyway, sorry, I hope they figure it out, but it's not something I've ever had trouble with. If it's an issue for you too, you might wanna write their support or just don't use the IDE.