`traceDeps` fails to trace nested dependencies in .pnpm folder

[katywings]

Environment

Versions

• node: v24.13.0
• nitro: 3.0.260610-beta
• pnpm: 10.30

Config

{
  traceDeps: ["sharp", "bcrypt"]
}

Reproduction

1. Use pnpm as package manager
2. Install and import dependency xyz that internally depends on a non-bundleable dependency such as sharp or bcrypt
3. Add sharp / bcrypt to nitro's traceDeps array
4. pnpm build

Describe the bug

Nitro / nf3 fail to trace nested dependencies of dependencies inside node_modules/.pnpm.

Additional context

Resolve Aliasing

I first tried to fix this issue, by adding an alias for the failing traces like below. Said alias fixed the result of rolldown's resolve at

nitro/src/build/plugins/externals.ts

Line 91 in 6de81ee

let resolved = await this.resolve(id, importer, rOpts);

, but nitro still failed to trace the dependency later down the line at

nitro/src/build/plugins/externals.ts

Line 119 in 6de81ee

if (!tryResolve(importId, importer)) {

.

{
   rolldownConfig: {
      resolve: {
        alias: {
          "sharp": "path/to/node_modules/.pnpm/sharp-xyz"
        }
      }
    }
}

Functioning workaround

By adding the failing dependencies to pnpms publicHoistPattern, they will be installed directly in node_modules and can be traced my nitro / nf3

# pnpm-workspace.yaml:
publicHoistPattern:
  - "sharp"
  - "bcrypt"

Logs

[pi0]

Thanks for issue @katywings! I guess saw this issue before and yeah installing top level is one workaround. Can you please report it upstream to https://github.com/unjs/nf3 ?

[katywings]

@pi0 I am sorry for the delay, just created the copy of the issue upstream 🙂👍