Our editor integration is completely editor agnostic. Deno implements the Language Server Protocol [1], which essentially all editors support. Because of this the new inlay hints feature, is supported on all editors that support inlay hints and use our LSP integration. The Jetbrains integration for Deno uses our LSP, but I don't know if they support inlay hints yet.

You can find docs on using Deno LSP with other editors here: https://deno.land/manual/getting_started/setup_your_environm...

[1]: https://microsoft.github.io/language-server-protocol/

I've been using Deno on neovim and it's been a breeze

An editor is an editor, why on earth would it bother you that someone uses a different editor than you?

Is this Jeopardy? Your question is essentially answered by his original comment.

Pardon? I am asking OP why he's annoyed that the post mentions VSCode. It's not normal to be annoyed at the mere mention of a text editor.

You should work on 1. your reading comprehension, and 2. making relevant comments to the discussion at hand.

They're not annoyed that the post mentions VSCode. They're annoyed that, from their experience, only VSCode is being supported.

VSCode is the only integration that the Deno core team maintains and develops. A rough poll indicates that about 80% of Deno users use vscode.

JetBrains/WebStorm now utilises the Deno language server directly (the same one that the VSCode integration uses) but they control how features are expressed in their client and when they deliver them, something the core team can't directly control.

So for various reasons, VSCode ends up being the focus.