wrangler deploy silently exits with code 1 on Node.js v26 after banner (no error message)

[m7md1alaa]

What versions & operating system are you using?

System:
OS: macOS 26.5.1
CPU: (8) x64 Apple M1
Memory: 423.53 MB / 8.00 GB
Shell: 4.0.2 - /usr/local/bin/fish
Binaries:
Node: 26.1.0
npm: 11.13.0
bun: 1.3.13
npmPackages:
wrangler: ^4.100.0 => 4.100.0

Please provide a link to a minimal reproduction

https://github.com/m7md1alaa/spot-healer

Describe the Bug

Running npx wrangler deploy (or node node_modules/wrangler/bin/wrangler.js deploy) prints the wrangler banner then silently exits with code 1. No error message is printed to stdout or stderr. The same command works correctly when run with Bun (bun --bun wrangler deploy).
WRANGLER_LOG=debug shows "event":"wrangler command errored" with "errorType":"Error" but does not surface the actual error text.

Please provide any relevant error logs

No response

[tsushanth]

Reading through the error paths on main to narrow the area:

1. The yargs command handler's try/catch at packages/wrangler/src/core/register-yargs-command.ts:358-396 calls handleError(err, args, argv) before re-throwing as CommandHandledError. So whatever path you're on does enter handleError.

2. handleError (packages/wrangler/src/core/handle-errors.ts) dispatches by error shape. Each typed branch (auth, certificate, file-not-found, raw-mode, ParseError, JsonFriendlyFatalError, build failure, Cloudflare APIError, etc.) writes its own user-facing message. The fallback else at L596-621 calls logger.error(loggableException.message ?? loggableException) — so a plain Error with a message should still reach the terminal.

3. The fact that WRANGLER_LOG=debug surfaces "event":"wrangler command errored" with "errorType":"Error" means the error class is the bare Error constructor — so you're landing in the fallback else branch of handleError, not in any of the typed branches.

A few things that would help pin this down:

• Full debug output: WRANGLER_LOG=debug npx wrangler deploy 2>&1 | head -200 — the debug channel separately logs loggableException.stack at L615 right after the user-facing logger.error() call; if stack is present but the message line above it isn't, that's a logger-level filtering issue specific to Node 26, not a missing-error issue. If neither is present, the error path doesn't reach handleError at all and the swallow is upstream.

• The exact error object: under your local node_modules, you can patch handle-errors.ts L609-616 to:

  process.stderr.write(`[debug-handle-errors] ${JSON.stringify({
    name: loggableException?.name,
    message: loggableException?.message,
    keys: Object.keys(loggableException ?? {}),
  })}\n`);

  and re-run. That bypasses the wrangler logger entirely; if you see that line but not the regular logger.error output, the bug is in the wrangler logger on Node 26 (not in error capture).

• The Bun-vs-Node split is the strongest hint. Bun reports successfully, Node 26 silently exits. So this is likely a Node 26-specific stdout/stderr interaction. Worth checking: do you see the error if you do npx wrangler deploy 2>/dev/null (only stdout)? Or npx wrangler deploy 1>/dev/null (only stderr)?

Happy to put up a focused PR once we know which of those three places the actual swallow is happening.

[jamesopstad]

Hi @m7md1alaa. I'm not able to reproduce this issue using Node.js v26. Does it still persist for you? If so, can you provide clear steps for how to reproduce? Thanks