The most straightforward option would probably be to write an LSP wrapper around the stack graphs code. One of the people on my team wrote a very “contrib directory” version of that for internal testing, which lets us test our stack graph rules for a new language in something like VS Code before deploying to production. If someone were to write a more polished version of that, that would be a great way to get code nav into any LSP-compatible editor for any language that supports stack graphs.

> One of the people on my team wrote a very “contrib directory” version of that for internal testing

If that is open-source, could you please share a link to it?

I'm curious what advantages this "stack-graphs LSP wrapper" has over existing language-specific LSP servers for an editor/IDE, maybe lower memory usage or better performance?

NeoVim has Tree-sitter and Language Server integration. I couldn't make it work for me, bit lots of people really love it!

If you haven't tried again recently the neovim team has done a ton of work updating the documentation on nvim-lspconfig [1]. There's also projects like kickstart.nvim [2] which aim to provide a very simple starting point for new users. It's "batteries-included" neovim which notably includes LSP, TreeSitter, completion engines, and some basic git functionality.

[1] https://github.com/neovim/nvim-lspconfig [2] https://github.com/nvim-lua/kickstart.nvim

Jump over to neovim with built-in lsp + treesitter .. and enjoy :)

(happy to help clarify setup/configuration)