[🐛 Bug]: getRequestContext in root layout says it needs to be on edge runtime even though that has been set

[eliw00d]

next-on-pages environment related information

System:
Platform: linux
Arch: x64
Version: #1 SMP Tue Nov 5 00:21:55 UTC 2024
CPU: (16) x64 AMD Ryzen 7 7800X3D 8-Core Processor
Memory: 15 GB
Shell: /usr/bin/zsh
Package Manager Used: npm (10.9.0)

Relevant Packages:
@cloudflare/next-on-pages: 1.13.5
vercel: 39.1.1
next: 15.0.3

Description

Currently, if I set runtime in my root layout to edge and call a lib function that uses getRequestContext to initialize my database, I get the following error:

▲  Error: `getRequestContext` and `getOptionalRequestContext` can only be run
▲  inside the edge runtime, so please make sure to have included
▲  `export const runtime = 'edge'` in all the routes using such functions
▲  (regardless of whether they are used directly or indirectly through imports).

If I do the same thing in a page, it works.

Reproduction

import { initializeDatabase } from '@/lib/utilities'

export const runtime = 'edge'

export default async function RootLayout({ children }: PropsWithChildren) {
  await initializeDatabase() // throws an error

  ...
}

Pages Deployment Method

Direct Upload (wrangler pages publish or the @cloudflare/pages-action GitHub Action)

Pages Deployment ID

No response

Additional Information

No response

Would you like to help?

• Would you like to help fixing this bug?