`fetch('/')` in the Repl causing infinite errors

[jasnell]

Version

24.7.0

Platform

All

Subsystem

repl

What steps will reproduce the bug?

Open the repl, type fetch('/'). ... (the period at the end triggers it)

How often does it reproduce? Is there a required condition?

Always

What is the expected behavior? Why is that the expected behavior?

It should print a single error because the URL is not absolute...

What do you see instead?

The repl enters a busy loop trying to parse the URL over and over

...
> Uncaught [TypeError: Failed to parse URL from /] {
  [cause]: TypeError: Invalid URL
      at new URL (node:internal/url:826:25)
      at new Request (node:internal/deps/undici/undici:10150:25)
      at fetch (node:internal/deps/undici/undici:10920:25)
      at fetch (node:internal/deps/undici/undici:15443:10)
      at fetch (node:internal/bootstrap/web/exposed-window-or-worker:83:12)
      at REPL199480:1:7
      at ContextifyScript.runInThisContext (node:vm:137:12)
      at REPLServer.defaultEval (node:repl:599:22)
      at bound (node:domain:433:15)
      at REPLServer.runBound [as eval] (node:domain:444:12) {
    code: 'ERR_INVALID_URL',
    input: '/'
  }
}
> Uncaught [TypeError: Failed to parse URL from /] {
  [cause]: TypeError: Invalid URL
      at new URL (node:internal/url:826:25)
      at new Request (node:internal/deps/undici/undici:10150:25)
      at fetch (node:internal/deps/undici/undici:10920:25)
      at fetch (node:internal/deps/undici/undici:15443:10)
      at fetch (node:internal/bootstrap/web/exposed-window-or-worker:83:12)
      at REPL199481:1:7
      at ContextifyScript.runInThisContext (node:vm:137:12)
      at REPLServer.defaultEval (node:repl:599:22)
      at bound (node:domain:433:15)
      at REPLServer.runBound [as eval] (node:domain:444:12) {
    code: 'ERR_INVALID_URL',
    input: '/'
  }
}
> Uncaught [TypeError: Failed to parse URL from /] {
  [cause]: TypeError: Invalid URL
      at new URL (node:internal/url:826:25)
      at new Request (node:internal/deps/undici/undici:10150:25)
      at fetch (node:internal/deps/undici/undici:10920:25)
      at fetch (node:internal/deps/undici/undici:15443:10)
      at fetch (node:internal/bootstrap/web/exposed-window-or-worker:83:12)
      at REPL199482:1:7
      at ContextifyScript.runInThisContext (node:vm:137:12)
      at REPLServer.defaultEval (node:repl:599:22)
      at bound (node:domain:433:15)
      at REPLServer.runBound [as eval] (node:domain:444:12) {
    code: 'ERR_INVALID_URL',
    input: '/'
  }
}
> Uncaught [TypeError: Failed to parse URL from /] {
  [cause]: TypeError: Invalid URL
      at new URL (node:internal/url:826:25)
      at new Request (node:internal/deps/undici/undici:10150:25)
      at fetch (node:internal/deps/undici/undici:10920:25)
      at fetch (node:internal/deps/undici/undici:15443:10)
      at fetch (node:internal/bootstrap/web/exposed-window-or-worker:83:12)
      at REPL199483:1:7
      at ContextifyScript.runInThisContext (node:vm:137:12)
      at REPLServer.defaultEval (node:repl:599:22)
      at bound (node:domain:433:15)
      at REPLServer.runBound [as eval] (node:domain:444:12) {
    code: 'ERR_INVALID_URL',
    input: '/'
  }
}
> zsh: killed     node

Additional information

No response

[minzunim]

@jasnell I tried to reproduce this issue, but in my environment I only see a single error message printed.
Could you please provide additional details on how to reproduce the infinite loop?

My environment:

• Node.js version: 24.7.0
• OS: Windows 11

[targos]

Can't reproduce either (v24.7.0 on macOS)

[jasnell]

The report is incomplete, you need to type fetch('/'). .. the period at the end is significant. I believe #59774 fixes this.