Next.js 15 server-side requests not captured — --require flag in PATH override not inherited by worker processes

Description

After updating Proxyman to 6.6.0 (from a version ~2 months ago), server-side requests from a Next.js 15 app are no longer visible in Proxyman. Nothing else changed, same Next.js version, same Node.js version, same setup.

The PATH override (overrides/path/node) injects Proxyman's script via --require on the initial node process. However, Next.js 15 spawns child worker processes for server components and route handlers. These workers invoke node directly and don't inherit the --require flag, so Proxyman's global-agent/undici patching is never applied to the processes that actually make HTTP requests.

Steps to Reproduce

1. Source the Proxyman automatic setup script in a terminal
2. Start a Next.js 15 app (next dev)
3. Trigger a server-side fetch (server component, API route, etc.)
4. Observe that the request does NOT appear in Proxyman

Note: Plain Node.js fetch works fine: node -e "fetch('https://httpbin.org/get').then(r => r.json()).then(console.log)" does appear in Proxyman.

Current Behavior

Server-side requests made by Next.js 15 worker processes are not captured by Proxyman. The --require injection from the PATH override only applies to the initial node process, not to child workers spawned by Next.js.

Expected Behavior

All server-side requests from Next.js should appear in Proxyman, as they did before the update.

Workaround

Using NODE_OPTIONS instead of the PATH override works because it's inherited by all child processes:

NODE_OPTIONS="--require /Applications/Proxyman.app/Contents/Frameworks/ProxymanCore.framework/Versions/A/Resources/overrides/js/js.min.js" next dev

Environment

• App version: Proxyman 6.6.0
• macOS version: macOS 26.2 (Tahoe)
• Node.js: v22.16.0
• Next.js: 15.3.6