Can not access request variable in api route

[byn9826]

Describe the bug

When I try to access the "request" variable inside app route api route, it throw "Error: The request.page has been deprecated in favour of URLPattern"

Steps to reproduce

1. create a route.ts file under app/api/
2. Define a put request

export async function PUT (
  request: Request, context: { params: Params },
) {
  console.log(request)
}

3. send a put request
   The output of "request" is:

<Formatting threw (Error: The request.page has been deprecated in favour of `URLPattern`.
  Read more: https://nextjs.org/docs/messages/middleware-request-page

    at get page (file:///Users/baozier/Projects/melody-auth/admin-panel/.open-next/server-functions/default/handler.mjs:10834:15)
    at Reflect.get (<anonymous>)
    at R.get (file:///Users/baozier/Projects/melody-auth/admin-panel/.open-next/.next/standalone/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:10781)
    at Object.get (file:///Users/baozier/Projects/melody-auth/admin-panel/.open-next/.next/standalone/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:29248)
    at Proxy.formatJsgResourceType (node-internal:internal_inspect:2383:31)
    at formatValue (node-internal:internal_inspect:813:49)
    at inspect (node-internal:internal_inspect:397:12)
    at formatWithOptionsInternal (node-internal:internal_inspect:2229:44)
    at formatWithOptions (node-internal:internal_inspect:2093:12)
    at formatLog (node-internal:internal_inspect:2318:16))>

Expected behavior

Should not throw error

@opennextjs/cloudflare version

experimental

Node.js version

22.x

Wrangler version

3.95.0

next info output

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:11 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 22.6.0
  npm: 10.8.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.14 // An outdated version detected (latest is 15.1.0), upgrade is highly recommended!
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
Next.js Config:
  output: N/A

Additional context

No response

[vicb]

It looks like a legit Next error triggered by accessing request.page via logging the request. The obvious fix is remove the log.

Does 'next dev' behaves differently?

[byn9826]

Next dev won't throw error.

https://nextjs.org/docs/app/api-reference/file-conventions/route#request-optional

For api route, Request is a valid param, and in post/put request, it is used to get the request payload

const reqBody = await request.json()

Because request is "<Formatting threw (Error: The request.page has been deprecated in favour of URLPattern.", so await request.json() will throw [object object] is not valid json error

[vicb]

Sorry I think my previous message was not very clear.

For api route, Request is a valid param, and in post/put request, it is used to get the request payload

Yes, we agree on that.

It is used in the API example and works fine.

From the error message, the problem is that request.page is accessed and this is what throws.

It is accessed because logging request will iterates the props and log request.page. There should be not problem logging request.<prop> for non deprecated prop.

But if console.log(request) works with next dev then we should take a deeper look.

Does this make more sense?

[vicb]

Oh wait.

So the console.log throwing is expected.

But the actual issue you have here is [object object] is not valid json error - I merged a PR fixing that this morning.

Please update to the HEAD of the experimental branch and that should fix your issue.

[byn9826]

This works well now, thank you!

[vicb]

Thanks for reporting!