[BUG] treesitter missing norg_meta parser

[vendion]

Field	Description
Plugin	treesitter neorg
Nixpkgs	unstable
Home Manager	unstable

• I have read the FAQ and my bug is not listed there.

Description

When working in a Neorg file, when I try to run :Neorg generate-workspace-summary the following error is displayed.

Error executing Lua callback: ....10.2/share/nvim/runtime/lua/vim/treesitter/language.lua:0: no parser for 'norg_meta' language, see :help treesitter-parsers
stack traceback:
	[C]: in function 'error'
	....10.2/share/nvim/runtime/lua/vim/treesitter/language.lua: in function 'add'
	...d-0.10.2/share/nvim/runtime/lua/vim/treesitter/query.lua: in function ''
	...iled-0.10.2/share/nvim/runtime/lua/vim/func/_memoize.lua: in function 'ts_parse_query'
	...ua/neorg/modules/core/integrations/treesitter/module.lua: in function 'get_document_metadata'
	...es/start/neorg/lua/neorg/modules/core/summary/module.lua: in function <...es/start/neorg/lua/neorg/modules/core/summary/module.lua:0>
	...ck/myNeovimPackages/start/neorg/lua/neorg/core/utils.lua: in function 'read_files'
	...es/start/neorg/lua/neorg/modules/core/summary/module.lua: in function 'strategy'
	...es/start/neorg/lua/neorg/modules/core/summary/module.lua: in function 'generate_workspace_summary'
	...es/start/neorg/lua/neorg/modules/core/summary/module.lua: in function 'on_event'
	.../myNeovimPackages/start/neorg/lua/neorg/core/modules.lua: in function 'broadcast_event'
	...s/start/neorg/lua/neorg/modules/core/neorgcmd/module.lua: in function <...s/start/neorg/lua/neorg/modules/core/neorgcmd/module.lua:0>

Minimal, Reproducible Example (MRE)

programs.nixvim = {
    plugins = {
neorg = {
        enable = true;
        # package = pkgs.stable.vimPlugins.neorg;
        modules = {
          "core.defaults" = {
            __empty = null;
          };
          "core.concealer" = {
            config = {
              iconPreset = "diamond";
            };
          };
          "core.dirman" = {
            config = {
              workspaces = {
                notes = "~/.local/share/neorg/notes";
                work = "~/.local/share/neorg/work";
                nix = "~/.config/nix/docs";
                rowlogic = "~/work/RowLogic/notes";
              };
              autoDetect = true;
              autoChdir = true;
              defaultWorkspace = "notes";
            };
          };
          "core.completion" = {
            config = {
              engine = "nvim-cmp";
            };
          };
          "core.export" = {
            __empty = null;
          };
          "core.export.markdown" = {
            __empty = null;
          };
          "core.presenter" = {
            config = {
              zen_mode = "zen-mode";
            };
          };
          "core.esupports.metagen" = {
            config = {
              type = "auto";
            };
          };
          "core.journal" = {
            config = {
              workspace = "notes";
            };
          };
          "core.summary" = {
            __empty = null;
          };
          "core.qol.todo_items" = {
            config = {
              create_todo_parents = true;
            };
          };
          "core.integrations.image" = {
            __empty = null;
          };
          "core.latex.renderer" = {
            __empty = null;
          };
          "core.ui.calendar" = {
            __empty = null;
          };
          "core.todo-introspector" = {
            __empty = null;
          };
        };
      };
        treesitter = {
            enable = true;
            folding = true;
            settings = {
              highlight.enable = true;
               incremental_selection.enable = true;
              indent.enable = true;
            };
          };
    };
}

[khaneliman]

Duplicate of #2345 . Been meaning to look into why it's not part of the upstream treesitter grammars that are bundled.

[vendion]

Ahh, that issue is marked as closed, which is why I missed it. For now. I'll look into using the workaround you mentioned in the other issue.

[MattSturgeon]

Ahh, that issue is marked as closed, which is why I missed it.

Seems the original poster closed it after finding a workaround. The underlying issue is still present. I guess this ticket can "take over" as the tracking issue.