Rescript in neovim

1

Hi,

I’m trying rescript in neovim for the first time. I’ve got some problem with the error reporting.

First I didn’t have any error reporting, other than syntax errors. Then, I found that enabling these options helped:

incrementalTypechecking = { enabled = true },
codeAnalyzer = { enabled = true },

Now when a file has an error (a type error), it will get reported as expected.
So I update my code to fix the error. But now the error is still reported, and it will never go until I restart the editor.
In other words the errors are not cleared even after being fixed.

Also, it seems to not report more than one error per file. Only the first type error is reported.

I installed it via Mason (rescriptls), and below is the exact config I put in lspconfig for rescript:

        rescriptls = {
          settings = {
            rescript = {
              -- opt-in experimental type-checking
              incrementalTypechecking = { enabled = true },
              -- deeper semantic analysis
              codeAnalyzer = { enabled = true },
            },
          },
        },

I haven’t found much resource on how to set it up well. Any help would be welcome!
Thanks

2

Paging some Neovim users @aspeddro @shulhi @dkirchhof @DCKT @CarlOlson

1 Like
3

Hey,

since language server version 1.62 or 1.63 you have to track for file changes by your own.
So you can add the capabilities field to the lsp config:

capabilities = {
    workspace = {
        didChangeWatchedFiles = {
            dynamicRegistration = true,
        },
    },
}

After adding this config, the lsp will update the errors after saving files.

If you use nvim-lspconfig, I added this information to their wiki (nvim-lspconfig/doc/configs.md at master · neovim/nvim-lspconfig · GitHub) and will add the config as default after the release of rescript 12.

2 Likes
4

@dkirchhof thanks for your help. Unfortunately the issue is still here after I enabled dynamicRegistration. I still need to restart the LSP to see things changing.

I also noticed that it’s not working well if I don’t start rescript compiler in watch mode rescript -w. It seems that the lsp used the build directory to detect issue rather than the code itself.

the lsp is version 1.66.0…

that’s what I’ve got in my config so far:

        rescriptls = {
          cmd = {
            "node",
            "/home/xxx/.local/share/nvim/mason/packages/rescript-language-server/node_modules/@rescript/language-server/out/cli.js",
            "--stdio",
          },
          capabilities = {
            workspace = {
              didChangeWatchedFiles = {
                dynamicRegistration = true,
              },
            },
          },
          settings = {
            rescript = {
              -- codeLens = true,
              incrementalTypechecking = {
                acrossFiles = true,
                enabled = true,
              },
              -- codeAnalyzer = { enabled = true },
            },
          },
        },
5

Your assumption is right, the language server doesn’t inspect the code, it uses the compiler output to check for errors and warnings.
So you have to start neovim in the root directory (where the rescript.json file is located) and the compiler in watch mode (rescript watch in the newest alpha / beta versions).

Your config looks similar to mine. Don’t know, if the settings field is correct?!
Here is my config (language server 1.66.0, installed as global node module):

rescriptls = {
    cmd = { 'rescript-language-server', '--stdio' },
    init_options = {
        extensionConfiguration = {
            askToStartBuild = false,
            incrementalTypechecking = {
                enabled = true,
            },
        },
    },
    capabilities = {
        workspace = {
            didChangeWatchedFiles = {
                dynamicRegistration = true,
            },
        },
    },
}
1 Like
6

@dkirchhof thanks for sharing your configuration. It’s still not working for me. So there is definitely something off. I’ll have to upgrade my neovim and lazyvim to latest, but that’s a breaking upgrade. I’ll do that later when I have enough time to migrate everything.

I’ll keep this thread up my sleeve and let you whether it worked.