Not sure what you mean by caching correctly? You typically don't cache pages when you do SSR
Not 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"] in wrangler.toml but on publish, the deployed result says it must be enabled from dash
CSo all bindings and config must be done from dashboard?
HYes
CI'm getting this error when trying to call
getRequestContext
CI have this in next.config.mjs:
CI'm on @cloudflare/next-on-pages version 1.9.0
CDo I not need to use getRequestContext?
CThe example included with the S3 next on pages uses it, but on the Cloudflare Docs, it just uses process.env https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site
Cloudflare Docs
Deploy a full-stack Next.js site (recommended).
Dare you calling the
getRequestContext
CI switched to using
process.envAnd yeah, I'm calling from the edge runtime
Dcould you provide a reproduction of it? if 
process.envgetRequestContextI found the issue, I didn't add
export const runtime = "edge";Cprocess.envah! 
Dweird.... what were you trying to access?
Can env variable
Dcould it be that in 
process.envI think what happened is the nextjs dev server loaded
.envprocess.envyeah, it does that 
CI had it in
.envok yeah that makes sense then 
XD@conqr ᯅ I'll improve our error message to remind developers to use the edge runtime , hopefully this can help avoid developers confusion/frustration: https://github.com/cloudflare/next-on-pages/issues/674
, hopefully this can help avoid developers confusion/frustration: https://github.com/cloudflare/next-on-pages/issues/674GitHub
We've recently made the getRequestContext local error more helpful, reminding people to set up the dev platform: next-on-pages/packages/next-on-pages/src/api/getRequestContext.ts Lines 52 to 61...
