aube with shims doesn't work properly

[skoch13]

Having packages installed

 aubr lint
  × binary not found: oxlint
  │ Try running `aube install` first, or check that the package providing 'oxlint' is in your dependencies.

Another example:

aubr build:dev
[rspack-cli] Error: spawn pnpm ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:287:19)
    at onErrorNT (node:internal/child_process:508:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn pnpm',
  path: 'pnpm',
  spawnargs: [
    '--filter',
    '@package',
    'build:dev'
  ]
}

[jdx]

Thanks for the follow-up. This appears to expose two related layers.

The original direct-script pnpm PATH regression from #1186 was fixed by #1187 and released in v1.37.0. The new binary not found: oxlint result suggests that the pnpm shim is now being reached, but the nested run/exec is resolving node_modules/.bin from the selected package only. If oxlint is declared at the workspace root while the command is running in a filtered member, the missing workspace-root bin fallback is the leading explanation.

The Rspack spawn pnpm ENOENT means the effective PATH in that descendant process does not contain the activated shim directory. v1.37.0 restores AUBE_SHIM_DIR for package scripts, but the current regression coverage checks a direct script invocation rather than a grandchild process spawning pnpm.

Could you share the output of:

aube --version
echo "$AUBE_SHIM_DIR"
command -v pnpm
aube bin
aube bin -w
ls -l "$(aube bin)/oxlint" "$(aube bin -w)/oxlint"

Please also share the relevant package.json scripts and whether oxlint is declared in the workspace root or the filtered package. That should let us distinguish a workspace-bin lookup gap from a PATH propagation issue and turn it into a focused regression test.

AI-assisted — Tool: Codex; model: unavailable; version: unavailable.

[skoch13]

I assume the issue is somewhere between pnpm workspace catalog decencies and npm workspace

1.37.0 macos-arm64 (2026-07-31)
/Users/%USER%/.local/share/aube/shims
/Users/%USER%/.local/share/aube/shims/pnpm
/%PATH_TO_PROJECT%/node_modules/.bin
%SAME AS ABOVE%
/%PATH_TO_PROJECT%/node_modules/.bin/oxlint
%SAME AS ABOVE%
"lint": "pnpm -r exec oxlint --no-error-on-unmatched-pattern ."

For rspack involved script it was "compile:my-prj": "pnpm --filter ./my/prj compile",

[jdx]

Thanks, this confirmed the cause. Catalog dependency resolution was not the problem; it exposed two separate PATH gaps:

• recursive exec searched only each workspace member’s node_modules/.bin, without pnpm’s workspace-root bin fallback
• the activated node shim sanitized the shim directory before handing off to real Node, so Node descendants such as Rspack could no longer spawn pnpm

Fixed in #1207. It adds workspace-root bin resolution/PATH propagation and restores the activated package-manager shims for real Node descendants without re-entering the Node shim. I also added regressions for sequential/parallel recursive exec and the node -> pnpm descendant path.

AI-assisted — Tool: Codex; model: openai/gpt-5; version: unavailable.

[skoch13]

will these be released anytime soon? I want to fully switch to aube, but this bug prevents me from it