We added KV because, well, people asked for it, but my personal opinion is that you should be using
We 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
16 Replies
are you using the same next-on-pages version in both the old and new deploy?
probably 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
ok, it was april 5 so i'll try 1.11.0
ok it seems to work fine with next-on-pages 1.11.0 @Better James
that's irritating - there's been a lot of changes since then...
can i be really annoying and ask if it's possible to increment the version until you get to the one that introduces the problem?
sure
thanks
1.11.3 works fine
1.12.0 has the error
:akoalathink:
do you use the fetch cache?
i don't have any code for controlling caching, but data does get cached. so i assume next does?
this is an app router project that has about 20 components that each do a fetch request
i'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
whether cached or not, there's no reason why one page would do more than ~20 subrequests 🤔
i agree, but that's the only thing related to those changes that would make sense
Now 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
Builder Day 2024: 18 big updates to the Workers platform
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...
Sounds 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.