"edge" runtime is not allowed in pages router getServerSideProps. "experimental-edge" is forced though it shouldn't be. #65945
Labels
bug
Issue was opened via the bug report template.
locked
Pages Router
Related to Pages Router.
Runtime
Related to Node.js or Edge Runtime with Next.js.
Link to the code that reproduces this issue
https://github.com/joulev/debug/tree/nextjs-pages-router-edge-page
To Reproduce
pnpm build
Current vs. Expected behavior
Current:
Expected:
While changing the runtime to
experimental-edge
does work, butedge
should work too. The documentation says so, hence either the documentation is wrong or the error should not be thrown. Since the edge runtime has been stable for a long time now, I think the bug is more in the code than in the documentation.Provide environment information
Operating System: Platform: linux Arch: x64 Version: #20~22.04.1-Ubuntu SMP Wed Apr 3 03:28:18 UTC 2024 Available memory (MB): 7930 Available CPU cores: 2 Binaries: Node: 18.20.2 npm: 10.5.0 Yarn: 1.22.19 pnpm: 9.1.0 Relevant Packages: next: 14.3.0-canary.70 // Latest available version is detected (14.3.0-canary.70). eslint-config-next: N/A react: 19.0.0-beta-04b058868c-20240508 react-dom: 19.0.0-beta-04b058868c-20240508 typescript: 5.4.5 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Pages Router, Runtime
Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), Vercel (Deployed)
Additional context
N/A
The text was updated successfully, but these errors were encountered: