I'd be up for helping fix the VSCode plugin. Note that I know little to nothing about VSCode plugins so if others are more experienced with it that'd be really helpful. Last time I tried it uses plenty of JS promises (ick) and it's hard to find the right docs. So it wasn't easy to just dive in and fix something, you probably need to take time to go through the intros / tutorials for VSCode plugins.
It might be better to modify / change `nimlsp` to use `nim check` instead. The LSP route lets you support multiple editors rather than just VSCode. Though the current LSPs don't seem to work at all for me. If we can get effort into these tools, it'd be great to have a Nim [debug adapter](https://microsoft.github.io/debug-adapter-protocol/). Hopefully it could just be a proxy to the Clang/GDB/VS debug adapters and demangle variable names and file locations.
