[🐛 Bug]: Response mismatch when using bindings in development via next-dev

[gcascio]

next-on-pages environment related information

System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
CPU: (10) arm64 Apple M1 Pro
Memory: 16 GB
Shell: /bin/zsh
Package Manager Used: npm (9.6.7)

Relevant Packages:
@cloudflare/next-on-pages: 0.0.0-dd15930 (prerelease for PR #612)
vercel: 33.0.2
next: 14.0.4

Description

I encountered an issue while using NextAuth V5 while using setupDevBindings from the next-dev package which I believe is related to following patch:

next-on-pages/internal-packages/next-dev/src/index.ts

Line 191 in 0a2008e

runtimeContext['Response'] = Response;

I encounter the following error

TypeError: "response" must be an instance of `Response`

The origin of this error lies in the oauth4webapi package which is used by NextAuth and does the following check in multiple places:

if (!(response instanceof Response)) {
  throw new TypeError('"response" must be an instance of Response')
}

I assume there is a mismatch between the patched and unpatched Response somewhere.

Reproduction

I created a minimal reproduction here. The auth flow works when setupDevBindings is commented out but as soon as setupDevBindings is used the aforementioned error occurs.

Pages Deployment Method

None

Pages Deployment ID

No response

Additional Information

No response

Would you like to help?

• Would you like to help fixing this bug?