Added a comment in the discussion [1] with a video and a quickstart guide on how you can configure VSCode to work with Deno. Let's continue the discussion there in case those steps don't work for you.
With respect to supporting other runtimes, it mostly comes down to focussing on providing a great experience with one runtime first. And based on your feedback, we still have some work to do there.
This looks like you're complaining that your development environment is not configured to work with Deno and is instead configured to process typescript files for a completely different runtime? Deno's tooling is top notch. The fact that most developers' systems are all setup for Node or some Node-based compilation step is hardly the fault of Deno.
Editors in general are still figuring how to have and manage configuration that is flexible enough for different language servers, linters, formatters, test runner, debuggers, etc. It's not really fair to either Deno or even your editor, though your editor is clearly more "at fault" in this scenario.
That one lol. Are there any solid reasons to not support other runtimes? Appwrite for example supports Nodejs.