also you should add a KV binding named ``__NEXT_ON_PAGES__KV_SUSPENSE_CACHE``
also you should add a KV binding named
__NEXT_ON_PAGES__KV_SUSPENSE_CACHE
Nbecause without it, caching is only at datacenter level
SYeah, the binding was already in place but no keys were saved before the force-cache 
NNi'm doing gaming websites
FThanks a lot though, seriously.
JIIRC force-cache is supposed to be the default but I guess we probably need to do some logic to apply it if no cache value is specified.
I'd be a bit hesitant to add that in now though considering we've had our fetch cache live for like 8 months and that kind of change would probably be breaking for a lot of users
I'd be a bit hesitant to add that in now though considering we've had our fetch cache live for like 8 months and that kind of change would probably be breaking for a lot of users
Jit's one of those things that would technically be a bug fix but in actuality would be a breaking change for almost all users who use fetch on the server
Pcould be added to documentation 
PHey Nob, if you ever find yourself in Sherbrooke, QC, Canada, hit me up, free beer on me!
Nahah, France is a bit far from Canada but maybe in 10 years x)
NI forgot I'm not even old enough to drink
N
Plà je comprends pourquoi tu ne comprenais pas quand je parle comme Yoda 
Mhey where do i put my functions for the cloudflare pages plugins
Mis it in the root dir or should i put inside /src or /src/app
N/app/api and you create api routes
Mcool
Tdo we have timeout for worker or page functions or nextjs api route?
Mdo tell me if im being dumb but anyone got any ideas what i did wrong ?
TThis error keeps happening even after I add
What could I be missing? I tried updating wrangler and workers types
compatibility_date = "2024-04-06" to my wrangler.toml.What could I be missing? I tried updating wrangler and workers types
HThat looks like something else? I’m guessing that whatever you are calling ImageService on isn’t actually supposed to be a binding?
JYou could probably just try implementing the server side validation example in the turnstile docs - https://developers.cloudflare.com/turnstile/get-started/server-side-validation/
Pages plugins will likely not work properly in Next.js api routes because they are written under the assumption that they'll be running in the functions directory, whereas here you just need a standard js solution instead
Pages plugins will likely not work properly in Next.js api routes because they are written under the assumption that they'll be running in the functions directory, whereas here you just need a standard js solution instead
Ldid the wrangler push changes get rolled back? i swear i was able to push a next on pages project without needing to setup anything in the dashboard in the last few days but now im back to needing todo that. 
Lalso seems like metrics arent being recorded at all for this deploy.
are metrics delayed?
are metrics delayed?
Jprobably better for pages-help
UTrying looking at the 30min chart sometimes that one is faster to populate
UOr whatever the shortest range of time is
JAny version of Next.js 14 should be perfectly fine
Ti'm trying to access a Service binding (RPC) in my Next-on-Pages. My wrangler.toml looks like this:
When I call it like this, running
It does not throw this error, indicating that the binding was found, but I get the following warning regarding RPC:
The "Image Search" is defined in my worker like this:
It does work when running
It does not work (and throws the error above) when running
Is it possible to make rpc service bindings work via next dev? Also since my vectorize worker do access Vectorize, it will only work via
When I call it like this, running
next devIt does not throw this error, indicating that the binding was found, but I get the following warning regarding RPC:
The "Image Search" is defined in my worker like this:
It does work when running
wrangler pages dev .vercel/output/static --service VECTORIZE_WORKER=vectorize-worker --compatibility-flag=nodejs_compat"wrangler devIt does not work (and throws the error above) when running
next devIs it possible to make rpc service bindings work via next dev? Also since my vectorize worker do access Vectorize, it will only work via
wrangler dev --remote
MAh OK do you think the mail channels plugin will work as well ?
MOr do you think I should just selfhost the website with nodemailer
Dhey i got quick question
Dis the 1 MiB limit per function or for the whole site?
Dhow do you debug/break down ur bundle size?
HFor the whole server bundle. This doesn't include static assets though. And the limit can be increased with a Workers Paid plan
Dye im thinking about buying the 10 MiB limit but even that seems very low as i have a simple app but already at 5 MiB
JIf you have a rather simple app at 5mb, maybe you have some chonky dependencies that are polluting the bundle
Leven if change it to 15 mins it’s not live as i was expecting.
Mwhere would i put the functions dir in a nextjs application using the app directory?
Msomone said just put them in /src/app/api
JYou would use Next.js API routes. The functions directory is not compatible with next-on-pages
J(also known as route handlers in the app dir)
Myhnx
Mgoing to make a thread
Lanyone know what’s up with this?
Jwhat wrangler changes are you referring to?
Lhttps://blog.cloudflare.com/pages-workers-integrations-monorepos-nextjs-wrangler the configure pages with wrangler part.
The Cloudflare Blog
Today, we’re launching four improvements to Pages that bring functionality previously restricted to Workers, with the goal of unifying the development experience between the two. Support for monorepos, wrangler.toml, new additions to Next.js support and database integrations!
