`bun run --filter` fails with `error: ENOENT` on Linux when using workspace glob patterns

[andredifs]

What version of Bun is running?

1.3.6+d530ed993 (also tested with 1.3.3)

What platform is your computer?

Linux x86_64 (Ubuntu 24.04 on GitHub Actions)

Note: Works correctly on macOS (Darwin 24.x arm64)

What steps can reproduce the bug?

1. Create a monorepo with multiple workspace glob patterns:

{
    "name": "bun-workspace-glob-bug",
    "private": true,
    "workspaces": [
        "packages/*",
        "dashboard",
        "functions/*"
    ]
}

2. Create the workspace packages:

   • dashboard/package.json with a simple script
   • packages/pkg-a/package.json
   • functions/func-a/package.json
   • functions/func-b/package.json

3. Run:

bun install
bun run --filter dashboard hello

Minimal reproduction repository: (I can create one if needed)

The issue occurs in our production monorepo with ~50 packages. When we changed from explicit workspace listings to glob patterns, the --filter command started failing on Linux CI while continuing to work on macOS.

What is the expected behavior?

The command should run the script in the matched workspace:

dashboard hello: Hello from dashboard
dashboard hello: Exited with code 0

What do you see instead?

On Linux (GitHub Actions):

error: ENOENT

That's the entire error message - no path information, no stack trace, no indication of what file or directory is missing. The command fails in ~4ms, suggesting bun fails during workspace/filter resolution before attempting to run the script.

Additional information

Key observations:

• bun install completes successfully
• The error only occurs when running --filter commands after install
• Works perfectly on macOS with identical setup
• Reverting to explicit workspace listings fixes the issue:

{
    "workspaces": [
        "packages/pkg-a",
        "dashboard", 
        "functions/func-a",
        "functions/func-b"
    ]
}

Possibly related: #24012 (ENOENT error reporting on Linux)

Request: Could the ENOENT error include more context (which file/directory is missing)? The current error message makes debugging very difficult.

[github-actions]

Found 3 possible duplicate issues:

1. ENOENT when filtering workspace packages #24951
2. Workspace package in camel case not found on Linux #21670
3. bun install --filter does not work if packages are listed explicitly rather than with packages/* glob #16715

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[andredifs]

Closing - couldn't reproduce with a minimal setup. Will add details to existing issue #11295 instead.

[andredifs]

Update: Reproducible! The issue is camelCase directory names on Linux

After further investigation, I was able to create a minimal reproduction:

Reproduction repo: https://github.com/andredifs/bun-workspace-glob-bug
Failed CI run: https://github.com/andredifs/bun-workspace-glob-bug/actions/runs/21296698449

Root cause

The issue occurs when workspace directories use camelCase names (e.g., funcA, funcB, pkgA) combined with glob patterns on Linux.

Minimal structure that fails on Linux:

.
├── package.json          # workspaces: ["packages/*", "functions/*"]
├── packages/
│   └── pkgA/             # camelCase ❌
└── functions/
    ├── funcA/            # camelCase ❌
    └── funcB/            # camelCase ❌

This is a duplicate of #21670

Issue #21670 describes the exact same problem: "Workspace package in camel case not found on Linux"

The underlying cause appears to be case-sensitivity handling differences between Linux (case-sensitive filesystem) and macOS (case-insensitive by default).

Workaround

Use kebab-case or explicit workspace listings instead of glob patterns with camelCase directories.