so something seems to have changed in how cloudflare handles these deploys, breaking my site
so something seems to have changed in how cloudflare handles these deploys, breaking my site
Ai rolled it back to the old deploy for now, since that's the only way for it to not error
JWe added KV because, well, people asked for it, but my personal opinion is that you should be using cache api since it aligns better with the expected behaviour of the fetch cache (e.g. being regional). And I'm also of the opinion that the eventual consistency of KV completely kills the ability for the cache to work properly because every change to the cache manifest takes 60 seconds to propagate which will mean it'll probably change every request when it shouldnt be
Jare you using the same next-on-pages version in both the old and new deploy?
Aprobably not, it isn't a dependency in the project, and the build command is
pnpm dlx @cloudflare/next-on-pages@1would you be able to try a deploy with next-on-pages version from when your last deploy worked and see if that makes the difference
Aok, it was april 5 so i'll try 1.11.0
Jthat's irritating - there's been a lot of changes since then...
Jcan i be really annoying and ask if it's possible to increment the version until you get to the one that introduces the problem?
Asure
Jthanks
A1.11.3 works fine
1.12.0 has the error
1.12.0 has the error
J
Jdo you use the fetch cache?
Ai don't have any code for controlling caching, but data does get cached. so i assume next does?
Athis is an app router project that has about 20 components that each do a fetch request
Ji'm thinking it's possibly something along the lines of those fetch requests might have been being cached before but one of these two fetch cache changes resulted in them not being cached either as long or at all and therefore leading to more requests happening
Awhether cached or not, there's no reason why one page would do more than ~20 subrequests 
Ji agree, but that's the only thing related to those changes that would make sense
INow that cloudflare has joined OpenNext, do we get a seperate channel for that or do we keep discussions around that in next-on-pages / next channel? https://blog.cloudflare.com/builder-day-2024-announcements/#cloudflare-joins-opennext
The Cloudflare Blog
To celebrate Builder Day 2024, we’re shipping 18 updates inspired by direct feedback from developers building on Cloudflare. This includes new capabilities, like running evals with AI Gateway, beta products like Queues and Vectorize graduating to GA, massive speed improvements to KV and Workers AI, pricing simplifications, and bringing key featu...
TSounds like OpenNext + Workers Static Assets will replace Pages so probably warrants a separate channel?
we plan to bridge the remaining gaps between Workers and Pages and provide ways to migrate your Pages projects to Workers.
Jthe blog post says to use the OpenNext Discord, so you should probably head over there for discussion about
@opennextjs/cloudflare
Dimo we need a migration guide from
@cloudflare/next-on-pages@opennextjs/cloudflare
BIs Cloudflare going to drop support for next-on-pages after OpenNext announcement? If so, a migration guide would be useful
SIs it correctly understood that ISR is not supported by next-on-pages? 
SOh, just saw the above blogpost regarding OpenNext... Interesting!
Jyou can't
KHello, as far as I know axios does not work on edge function right? but why is this api endpoint of mine working just fine
Jmagic
YGitHub
The goal of this PR is to add a minimal fetch implementation that provides the same capabilities as the xhr adapter without major changes, allowing it to be released in Axios 1.x.
To avoid breaking...
To avoid breaking...
CHello, trying to learn and try deploying an existing nextjs project to pages, I'm following the ssr guide. But I got a question.
In the docs, a library
In the docs, a library
@cloudflare/next-on-pagesSnyk Advisor
Find the best open-source package for your project with Snyk Open Source Advisor. Explore over 1 million open source packages.
Tnpm audits typically show a lot of stuff due to how many dependencies npm packages have (you'd need to double check the source of the 11 vulerabilities)... Majority of it (esp for dev deps) is not applicable. Most of the time you just need to re-generate the lock file which updates downstream dependencies
PAre Next.js Workers more expensive than Next.js Pages? Does one HTTP request equal one worker request?
Jit's the same
JPages uses workers
SAttempting to embed Sanity Studio into a Cloudflare Pages deploy and since it must run on edge it falls into the worker size limit
I am assuming my solution is to just upgrade to a paid plan to fit within the larger size limit and I'm not configuring something incorrectly here?
I am assuming my solution is to just upgrade to a paid plan to fit within the larger size limit and I'm not configuring something incorrectly here?
Jcorrect
TThat's not necessarily true, it's one request but can be more expensive. @Puliczek I replied to you on Open NextJS discord
TTldr: higher CPU and page load but limited testing
PThank you so much for your analysis. I will wait longer before migrating. Also, there is no proper tutorial on how to migrate from Pages to Workers.
面Middleware ？
JMiddleware works
AI keep having this problem, when I update next-on-pages, my project stops working with a "XMLHttpRequest is not defined" any idea how to troubleshoot this?
AI think i've mentioned it previously
Ayea soon as i force 1.9.0 everything works ok
Ayea, i knew i'd asked about it previously
JThat doesnt sound related to next-on-pages
