Error: attempt to call method `range` (a nil value) when in `sort` function

[AlejandroSuero]

Hi @laytan,

I am using neovim v0.12, and when trying to use TailwindSort on a .tsx file (I don't know for the rest of the filetypes), I get the following error:

Lua :command callback: /usr/local/share/nvim/runtime/lua/vim/treesitter.lua:179: attempt to call method 'range' (a nil value)
stack traceback:
        /usr/local/share/nvim/runtime/lua/vim/treesitter.lua:179: in function 'get_range'
        /usr/local/share/nvim/runtime/lua/vim/treesitter.lua:214: in function 'get_node_text'
        ...lazy/tailwind-sorter.nvim/lua/tailwind-sorter/tsutil.lua:23: in function 'get_match_text'
        ...t/lazy/tailwind-sorter.nvim/lua/tailwind-sorter/init.lua:54: in function 'sort'
        ...t/lazy/tailwind-sorter.nvim/lua/tailwind-sorter/init.lua:22: in function <...t/lazy/tailwind-sorter.nvim/lua/tailwind-sorter/init.lua:21>

I can try and look at it if I have time, but since I don't know treesitter as well as you, I will thank you in advance if you know what could be causing to not get the value and have nil instead.

[studious]

I'm getting the same error now in eruby as well

[chris-av]

Am using index.js and am getting the same error when writing to buffer. I am suspecting that something about the treesitter APIs have changed. But I am really out of my depth.

I tried to bug trace this. Is it perhaps the case that the shape of the TSNode has changed? I took a screenshot :

I see that tailwind-sorter.nvim/lua/tailwind-sorter/init.lua and tailwind-sorter.nvim/lua/tailwind-sorter/lua/tailwind-sorer/tsutil.lua have the same data flowing through them in the match object, which looks correct:

{
    buf = <int>,
    node = { <userdata> }
}

I also see that lua/tailwind-sorter/tsutil.lua is correctly passing a valid node value to the treeesitter code:

M.replace_match_text = function(match, text)
  local original = vim.treesitter.get_node_text(match.node, match.buf)
...

And this is where it breaks. I suspect that something about the node object has changed. :range() does not appear to be a valid method.

function M.get_range(node, source, metadata)
    if metadata and metadata.range then
        assert(source)
        return M._range.add_bytes(source, metadata.range)
    end
    return { node:range(true) }    -- does `node` have a valid `:range()` method?
end

This node value appears to take on the value of TSNode. Maybe the treesitter API has changed? I have successfully evaded runtime errors naively by passing an indexed value here :

-- tailwind-sorter.nvim/lua/tailwind-sorter/tsutil.lua:23
M.get_match_text = function(match)
  -- NOTE: pass indexed value, not the entire match.node
  local text = vim.treesitter.get_node_text(match.node[1], match.buf) 

  if match.offset then
    text = text:sub(match.offset.start_col, match.offset.end_col)
  end

  return text
end

This seems consistent with the print statement where in /usr/share/nvim/runtime/lua/vim/treesitter.lua, I am seeing { <userdata > } rather than just <userdata 1>.

[chris-av]

Possibly related.

neovim/neovim#27591 (comment)

[studious]

I'm trying to understand how a node might not be the right type when it gets to the range function.

If I print out each node I find most of them look like real nodes until it crashes on nil. The last node prints as a table.

function M.get_range(node, source, metadata)
    if metadata and metadata.range then
        assert(source)
        return M._range.add_bytes(source, metadata.range)
    end
    print(node)    -- what is this node
    return { node:range(true) }    -- does `node` have a valid `:range()` method?
end

...
<node attribute_name>
<node attribute_name>
table: 0x0101e09ec0
Error detected while processing BufWritePre Autocommands for "*.erb":
Error executing Lua callback: .../neovim/0.11.2/share/nvim/runtime/lua/vim/treesitter.lua:178: attempt to call method 'range' (a nil value)
stack traceback:
        .../neovim/0.11.2/share/nvim/runtime/lua/vim/treesitter.lua:178: in function 'get_range'
        .../neovim/0.11.2/share/nvim/runtime/lua/vim/treesitter.lua:213: in function 'get_node_text'
        ...lazy/tailwind-sorter.nvim/lua/tailwind-sorter/tsutil.lua:23: in function 'get_match_text'
        ...m/lazy/tailwind-sorter.nvim/lua/tailwind-sorter/init.lua:50: in function 'sort'

Is this adding a final odd node or is something else at play?

[redoxahmii]

Same issue here, is there anything told by the maintainer about this, or is it just a dead end at the moment?

[toto1384]

same issue

[Eht67]

same issue here