bug: Neovim hangs in pnpm workspaces monorepo

[AkisArou]

Neovim version (nvim -v)

v0.12.0-dev-1919+gddd6ac5083

Operating system/version

Arch linux

Describe the bug

After commit 42d15cd, Neovim freezes in a pnpm workspaces monorepo, when I run a task.
(Specifically it is an npm ts watch task)

No special config required.
just require("overseer").setup()

The freeze appears to be caused by this line of the resolve_workspace_paths function:

lua/overseer/template/npm.lua:88

local matches = vim.fn.glob(glob_path, false, true)

What is the severity of this bug?

blocking (cannot use plugin)

Steps To Reproduce

1. Create a pnpm workspaces project
2. Run a npm task

Expected Behavior

It should not freeze neovim

Minimal example file

No response

Minimal init.lua

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  { "stevearc/dressing.nvim", config = true },
  {
    "stevearc/overseer.nvim",
    config = function()
      require("overseer").setup({
        -- add your overseer config here
      })
    end,
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Additional context

I run the "ts:watch" task:
overseer.run_task({ name = "ts:watch" })

{
  "name": "example",
  "type": "module",
  "private": true,
  "scripts": {
    "ts:watch": "tsc --build --watch"
  },
  "engines": {
    "node": "24.11.0"
  },
  "packageManager": "pnpm@10.20.0+sha512.cf9998222162dd85864d0a8102e7892e7ba4ceadebbf5a31f9c2fce48dfce317a9c53b9f6464d1ef9042cba2e02ae02a9f7c143a2b438cd93c91840f0192b9dd"
}

[stevearc]

When you say "freeze," does it lock the UI thread for some long amount of time or does it block Neovim indefinitely?
Do you know what the glob_path is that is being passed to the function?
The only thing I can think of is that the glob pattern is very permissive and if you have a large repo it might take a long time to match all the files in it.

[AkisArou]

It blocks it indefinitely!
I waited for some minutes, and the glob_path is <repo_dir>/apps/**.
Of course there is <repo_dir>/packages/** etc.
It is not a large repo.

[stevearc]

That's surprising, as it would indicate that there's some sort of infinite loop or failure in the glob() implementation. Do you get the same freeze if you call it directly like :=vim.fn.glob("<repo_dir>/apps/**", false, true) or :echo glob('<repo_dir>/apps/**', v:false, v:true)? Is there any way to get some sort of minimal repro without your (presumably private) repository? If it really is an issue with glob() then we'll need to report this upstream on the Neovim repo, but they'll need a repro to do anything.

[AkisArou]

I run it manually in the repo and it still froze.
I run it in another directory and it worked.
I run it in a minimal workspace of the repo, it took 3-4 seconds, but it resolved.
It is a lot of work and there are symlinks/dependencies between local workspaces and also big node_module deps! (normal pnpm)
It would be good if this feature is opt-in/opt-out or a much performant solution is found!

Thanks for this great plugin!

[stevearc]

I've reverted the pnpm workspaces logic in fe4c8a0