Unable to load nvim-treesitter.ts_utils

[serpro69]

Prerequisites

• I am using the latest stable release of Neovim
• I am using the latest version of the plugin

Neovim Version

0.11.2

Neorg setup

return {
  "nvim-neorg/neorg",
  lazy = false,
  version = "*",
  opts = {
    load = {
      ["core.defaults"] = {}, -- Loads default behaviour
      ["core.concealer"] = { config = { folds = true, icon_preset = "varied" } }, -- Adds pretty icons to your documents
      ["core.keybinds"] = {
        config = {
          neorg_leader = ",",
        },
      },
      ["core.dirman"] = {
        config = {
          workspaces = {
            notes = "~/notes",
          },
          default_workspace = "notes",
        },
      },
    },
  },
}

Actual behavior

Expected behavior

Should not throw errors

Steps to reproduce

Switch to main branch of nvim-treesitter and nvim-treesitter-textobjects

Potentially conflicting plugins

No response

Other information

No response

Help

None

Implementation help

No response

[IpadDilectio]

I think I have the same problem.

[timhugh]

I ran into this as well. It's only an issue on the main branch of treesitter which introduced breaking API changes, but the master branch still works. I don't know the scope of the changes or how neorg interacts with treesitter, but the breaking changes are noted at the top of the treesitter readme: https://github.com/nvim-treesitter/nvim-treesitter?tab=readme-ov-file#nvim-treesitter

[chuan2984]

well, i did some of these upgrades for a few plugins that had this problem. The problem here is the outdated api, namely, ts_util and parser, a lot of these functions are upstreamed to neovim, one could make a local ts_util and ts_parser module so most of the internal API of this plugin dont have to change. It does require a few hours of work. I did just some preliminary search for ts_util, its doable. However, i was just going to try it out. Im tempted to just go back to obsidian.nvim for the time being.

[Necrom4]

Do we have an update concerning this? LazyVim forces using the main branch of nvim-treesitter which breaks neorg and I haven't found a way of solving this yet.

[sheldonj84]

FYI: LazyVim just went to the main branch of treesitter which is going to break a bunch of peoples neorg

[Necrom4]

@sheldonj84 Have you found a solution yet? l personally tried installing Neorg with Rocks but was unsuccesful, so I thought of pinning treesitter to the master branch but it conflicts with the LazyVim config that pins to the main branch. Lastly I tried installing tree-sitter-norg and adding a custom parser this way but I ran again into a Rocks issue and was unable to install it.

[imli700]

Yep the new lazyvim update completely broke neorg for me. I'm sorry for pinning and I know you're busy but @benlubas can you please look into this

[benlubas]

Sounds like a lazy vim problem to me. They're shipping a broken plugin.

But yeah we should switch over to main. It's about time.

[Necrom4]

@benlubas

Sounds like a lazy vim problem to me.

I created an issue there before comming here but Folke said:

Norg was never a default treesitter parser that was installed. You need to check the neorg repo and possibly file an issue there so that they make their plugin compliant with nvim-treesitter main.

Not a LazyVim issue....

So I guess neorg should be adapted to work with the main treesitter branch.

[benlubas]

You can obviously downgrade lazy vim in the meantime.

But yes, we absolutely do need to upgrade.