Regression on Response.constructor.name changed to _Response

[pi0]

Version

v18.18.2

Platform

Darwin / Linux

Subsystem

No response

What steps will reproduce the bug?

Evaluate in Node.js >= 18.18:

console.log(new Response().constructor.name)

or:

npx node@18.18 -e "console.log(new Response().constructor.name)"

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

No response

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

Response constructor name for all current versions of Node.js prior to 18.18 (including 18.17), Browsers (chrome), undici, node-fetch, Bun and Deno is Response.

What do you see instead?

The constructor name in newer Node.js distros is changed to _Response which is a breaking behavior change.

Additional information

Discovered while investigating unjs/nitro#1839

It seems a recent regression happening in the packaging process of Node.js dist as when checking undici source code the constructor name is Response correctly.

Logging constructor function, shows a semi-transpiled code:

[KhafraDev]

this is an issue with esbuild, I will fix it soon