Error: Range#create called with invalid arguments

[npearson72]

I'm running into a bug using your lovely extension (thank you for building it BTW)

Here's a screen recording demonstrating the issue:

Screen.Recording.2025-08-05.at.4.26.39.PM.mp4

Here's a minimum init.lua

local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"

if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    "--branch=stable", -- latest stable release
    lazypath,
  })
end

vim.opt.rtp:prepend(lazypath)

require("lazy").setup({
  "neoclide/coc.nvim",
  branch = "release",
  config = function()
    vim.g.coc_global_extensions = {
      'coc-oxc',
      'coc-tsserver',
    }
  end
})

Here is a repo you can test the issue on:

https://github.com/npearson72/coc-oxc-bug

It's a Vite app (although any jsx/tsx will cause the issue)

---

Here is the my CocInfo:

## versions

vim version: NVIM v0.11.2
node version: v23.9.0
coc.nvim version: 0.0.82-29774cf 2025-07-21 11:21:14 +0800
coc.nvim directory: /Users/nathan/.local/share/nvim/lazy/coc.nvim
term: tmux
platform: darwin

## Log of coc.nvim

2025-08-05T16:36:53.678 INFO (pid:36970) [plugin] - coc.nvim initialized with node: v23.9.0 after 95
2025-08-05T16:37:01.814 INFO (pid:36970) [services] - LanguageClient cssmodules state change: stopped => starting
2025-08-05T16:37:01.823 INFO (pid:36970) [services] - LanguageClient oxc state change: stopped => starting
2025-08-05T16:37:01.882 INFO (pid:36970) [services] - service tsserver started
2025-08-05T16:37:01.885 INFO (pid:36970) [language-client-index] - Language server "languageserver.cssmodules" started with 36976
2025-08-05T16:37:01.893 INFO (pid:36970) [language-client-index] - Language server "coc-oxc" started with 36978
2025-08-05T16:37:02.011 INFO (pid:36970) [services] - LanguageClient oxc state change: starting => running
2025-08-05T16:37:02.014 INFO (pid:36970) [services] - service coc-oxc started
2025-08-05T16:37:02.067 INFO (pid:36970) [services] - LanguageClient cssmodules state change: starting => running
2025-08-05T16:37:02.068 INFO (pid:36970) [services] - service languageserver.cssmodules started
2025-08-05T16:37:12.211 INFO (pid:36970) [attach] - receive notification: showInfo []
2025-08-05T16:37:18.828 INFO (pid:36970) [snippets-session] - Before and snippet body changed, cancel snippet session
2025-08-05T16:37:21.922 INFO (pid:36970) [snippets-session] - Content change before snippet, reset snippet position
2025-08-05T16:37:23.515 INFO (pid:36970) [attach] - receive notification: showInfo []

Here is the coc-settings.json I'm using for this test:

{
  "oxc.enable": true,
  "oxc.configPath": ".oxlintrc.json"
}

[npearson72]

@Boshen A bit more info for you.

I'm not a Rust dev, so I could only do a little tracing in coc-nvim. Logging here : https://github.com/neoclide/coc.nvim/blob/master/src/diagnostic/buffer.ts#L175C50-L175C64

The edit object looks like this:

{
  "range": {
    "start": {
      "line": 45,
      "character": 5
    },
    "end": {
      "line": 45,
      "character": 5
    }
  },
  "newText": ">"
}

Seems normal.

Then when it pulls the entries from the this.diagnosticsMap.entries()

It looks like this:

[
  "coc-oxc",
  [
    {
      "range": {
        "start": {
          "line": 2147483647,
          "character": 2147483647
        },
        "end": {
          "line": 2147483647,
          "character": 2147483647
        }
      },
      "severity": 1,
      "code": "",
      "source": "oxc",
      "message": "Unexpected token"
    }
  ]
]

Somewhere in OXC it's shooting up that line and character position. I doubt this is just a coc-nvim situation, although I can't be sure.

Hope this helps.

[Sysix]

The problem is on your editor side. Any Language Server could send this response to an editor.
2147483647 is the max allowed integer for LSP:
https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#baseTypes

VSCode and IntelliJ handle this correctly.

I improved the position output for parser / semantic errors:
oxc-project/oxc#14010

[npearson72]

The problem is on your editor side. Any Language Server could send this response to an editor. 2147483647 is the max allowed integer for LSP: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#baseTypes

VSCode and IntelliJ handle this correctly.

I improved the position output for parser / semantic errors: oxc-project/oxc#14010

I use neovim. This extension if for coc.nvim (for neovim).

Are you saying the issue is with coc.nvim, neovim, or specifically with my editor? Are you able to get this extension to work?

[fannheyward]

2147483647 is the max allowed integer for LSP

Yes, this value is allowed, but it's not a correct line number of a document.

[Sysix]

Yes, this value is allowed, but it's not a correct line number of a document.

I agree, and thanks for the reply.
Still, I think the problem should be fixed with the editor too. As long as the LSP specs are not allowing it, the server and the clients should handle each weird use case.
I am happy to fix it on the language server side for you, by setting unknown ranges to 0,0. I still hope I have a valid point here :')

[Boshen]

Released in https://github.com/oxc-project/oxc/releases/tag/oxlint_v1.17.0