getRequestContext from a next handler for local dev
getRequestContext
CCCC
D
getRequestContext
process.envprocess.envgetRequestContext
Cexport const runtime = "edge";Cprocess.env
DCDprocess.env
C.envprocess.env
C.env
XD , hopefully this can help avoid developers confusion/frustration: https://github.com/cloudflare/next-on-pages/issues/674CD
DD
CC
C
BB
BB
❯ yarn wrangler deploy .vercel/output/static/_worker.js/index.js --dry-run --compatibility-date 2024-02-22 --name test
BBD
wrangler pages deploywrangler deploy, can you try that? BBB
Dnode:async_hooks one), it's likely due to using the wrong commandDwrangler deploy somewhere? 
if so please let me know as that needs amending! 
BB
DWorkers documentation, not Pages documentation....Pages documentation 
BBDwrangler pages deploy@cloudflare/next-on-pages, then take the .vercel/output/static/_worker.js manually gzip it and check the gzip's output size 
BBDexport const runtime = "edge";❯ yarn wrangler deploy .vercel/output/static/_worker.js/index.js --dry-run --compatibility-date 2024-02-22 --name testwrangler deploywrangler deploynode:async_hooksWorkersPagesPages@cloudflare/next-on-pages.vercel/output/static/_worker.jsimport { setupDevPlatform } from "@cloudflare/next-on-pages/next-dev";
if (process.env.NODE_ENV === "development") {
await setupDevPlatform({});
}