I'm new to rescript so i wasn't doing it before.

To avoid an x/y problem: I'm trying to run rescript build and parse the output into my neovim quickfix panel. Parsing this cli output is proving tricky for me; hence the request for a more structured output.

Alright. I should be able to get something working with the build artifacts or with the Language Server. Might be the right time for me to learn LSP.

The LSP is leaving a lot to be desired, at least in Neovim. I'm finding it will only show diagnostics for open buffers and not for the whole project. So if a buffer is closed, it has no errors according to LSP until I try and build it with rescript build.

• https://artem.rocks/posts/workspace_diagnostics_nvim

Yes, LSP will only report diagnostics for the open files.
Can you describe one more time what you are actually after.
I still don't quite get your workflow.

I have a binding in one module that I'm exporting. In another module I am importing it and using it. My editor will not tell me of any errors if I change the binding in the exporting module. As soon as I open the file of the importing module it will tell me of an error.

Ideally I would like to be able to change a type or binding and be told everywhere where I need to update its usage. Exhaustive checks on a pattern match is a good example of where I'd like to see errors for when I add a member to a Tuple or Variant type.

Both buffers open, I see the error:

One buffer open, I do not see the error:

I do see that workspace diagnostics is something that LSP supports and Neovim nightly supports. However, it doesn't seem like rescript-language-server nor my stable Neovim supports it. Therefore, I believe I am left with looking for a structured output of npx rescript build --json or parsing the stdout/stderr with regex to get workspace diagnostics in my editor. Another good option for me is to use the terminal built into my editor and run the command there, that way I can easily open files from the error message still, but missing out on a lot of the infrastructure built around Diagnostics.

• https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_diagnostic
• https://github.com/search?q=repo%3Arescript-lang%2Frescript-vscode+workspace%2Fdiagnostic&type=code
• https://github.com/neovim/neovim/blob/c374d7809572976c608c3042ce11f72e5d1c7fd4/runtime/doc/news.txt#L257