SHey! I'm trying to return CSS in the <head> my NextJS app using the experimental-edge runtime so there isn't a flicker on load. This works fine when building statically, but it's not working when using SSR on experimental-edge . Has anyone else ran into this issue?
BI tried when using fetch and still no luck. When looking at some pull requests of next-on-pages previously revalidatePath/next cache and caching wasnt supported yet. Could you confirm that it is now?
JYes we implemented support for the fetch cache a long time ago. Please send code snippets of what you're doing
BYea i just found the pr, sorry for that. I will provide code snippets tomorrow
DThanks 
MHas anyone here successfully ran a next pages app with a D1 db locally?
I did follow this setup and configuration: https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/#use-bindings-in-your-nextjs-application
Unfortunately I am not having any luck getting this to run.
I did follow this setup and configuration: https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/#use-bindings-in-your-nextjs-application
Unfortunately I am not having any luck getting this to run.
CTrying to determine if SSR pages are caching correctly... Should I be seeing
cf-cache-status
Mhey! I'm getting this error when using Drizzle orm. Is this fixed? any workarounds for this?
PSame here. Completely blocked 
Omiddleware redirects like this
are changing the view but not the url in the url bar
I'm forced to use
return NextResponse.redirect(new URL("/auth", request.url));are changing the view but not the url in the url bar
I'm forced to use
router.pushrouter.refresh
GAnyone experienced an issue with trying to set multiple set-cookie headers being merged into one? I am using Auth.js and it fails, because of the session-token cookie and the code_verifier cookie are put both in one header.
GJust tried on Vercel. This works properly there. Is there any workaround for this in Cloudflare or should I move?
ISet-cookie headers are allowed to be merged as long as they're joined with a comma... is that what you're seeing? https://stackoverflow.com/a/2880070
GYes, this is what I am seeing. But it does not work as expected - the cookie is never actually set.
DHey @Georgi Vatsov, I think we had similar issues in the past, could you try using the latest version of next-on-pages? and if it doesn't work create a new issue (https://github.com/cloudflare/next-on-pages/issues/new?assignees=&labels=bug&projects=&template=bug-report.yml&title=%5B%F0%9F%90%9B+Bug%5D%3A+) with a minimal reproduction?
Dyeah.... I do feel like that should work! 
https://github.com/cloudflare/next-on-pages/blob/3846730c4a0d12cda128d691160968d0a131a6f1/packages/next-on-pages/tests/templates/utils/http.test.ts#L46-L54
https://github.com/cloudflare/next-on-pages/blob/3846730c4a0d12cda128d691160968d0a131a6f1/packages/next-on-pages/tests/templates/utils/http.test.ts#L46-L54GitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
JNot sure what you mean by caching correctly? You typically don't cache pages when you do SSR
JPlease open an issue if this is a bug
Bin examples why do you guys have
if this is the correct version:
if this is the correct version:
DHi,
I'm getting an issue deploying to CF Pages:
I'm getting an issue deploying to CF Pages:
DUnexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/blog/[slug].func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' is the culprit but I don't know anything about what could cause it
DDid you managed to fix your issue ?
MI removed the file that caused the issue and moved onto another problem, will come back to it though at some point.
DOk, I might aswell consider removing the blog but it's a main feature. Thank you for your feedback on this
MIt wasnโt anything to do with a blog that caused the issue for me. It was a file that generates custom open graph images.
MLooks like the same error though.
DI've been able to replicate on my local setup, in the .vercel/output/functions/blog/[slug].func, there is no wasm folder, only these two files:
index.js index.js.map
index.js index.js.map
JPlease can you open an issue on the next-on-pages repo
DYes but what about reproduction ? Can't provide a public access to my repo
Jit's something specific about the blog/[slug] page, so maybe you could take parts out of that page until you can reproduce it? possible it might be related to og images or something like that
DCould you help me by looking at the code ? I could provide you a sample of our code, the blog subfolder
MI'm subscribed to that issue.
Is there any timelines on when the fix will be live?
Is there any timelines on when the fix will be live?
MGitHub
next-on-pages environment related information No response Description Cloudflare build fails when using git integration on a minimal repository containing create-next-app and an additional file loc...
DWhen deleting the blog folder, the error move on to another folder, etc
DIt's a never ending error
Dis there anything specific to install for wasm to be generated
DOk so I've managed to find the issue
DDthis is what's causing the issue, deleted it
BI managed to get Next-on-pages working with D1 and drizzle and it works in production but am currently getting this error local:
I just run npm run dev with setupDevPlatform as stated in the docs
Code:
I just run npm run dev with setupDevPlatform as stated in the docs
Code:
CIs wrangler.toml ignored for next-on-pages
HOn deploy, yes
CI have
compatibility_flags = ["nodejs_compat"]
CSo all bindings and config must be done from dashboard?
HYes
