bug: `node_modules` are visited during workspace lookup in npm-based projects

[r4zendev]

Neovim version (nvim -v)

nightly

Operating system/version

MacOS Sonoma 14.3

Describe the bug

In any JavaScript/TypeScript monorepo which has multiple nested packages and non-hoisted node_modules folders - the node_modules of those workspaces are still being walked and makes the neovim instance freeze for unreasonable amount of time and add tasks from installed modules making it really annoying and hard to work with. A possible workaround is to check for whether currently walked directory matches node_modules, which I tested myself locally and submitted a PR for in #485

What is the severity of this bug?

tolerable (can work around it)

Steps To Reproduce

1. open any medium-/high- sized TypeScript monorepo with multiple packages and non-hoisted node_modules
2. Open neovim and run :OverseerRun
3. Get your Neovim frozen for like 10-20 seconds before the task list is parsed

Expected Behavior

Avoid node_modules during traversing

Minimal example file

No response

Minimal init.lua

Additional context

No response

[r4zendev]

I guess it's worth mentioning that this likely happens due to pnpm-workspace.yaml file usually specifying the workspaces in the following format:

packages:
  - apps/*
  - libs/**

which probably makes the plugin think that it should traverse everything down the file tree. But we should probably omit node_modules in any cases nonetheless.

[gogamid]

i would like add that last working commit (usable without neovim freezing) is afbac6c, i pinned it before it is resolved.

  {
    "stevearc/overseer.nvim",
    commit = "afbac6c612b12772591640d801fad65423af02b9", --slow performance
}

[stevearc]

I've reverted the pnpm workspaces logic in fe4c8a0