Just to clarify, I don't mean being charged for Pro plan but for Workers Paid
Just to clarify, I don't mean being charged for Pro plan but for Workers Paid
EHaha, yes both 
Thanks for clarifying that though
Thanks for clarifying that though
CWell I'd wait for that incident to be over and then see. I mentioned in the escalation thread for it that error as well. It's possible you may need to billing ticket since it charged you. It seems to be all new subscriptions are broken rn
EI see. I'll give it until tomorrow to see if it's fixed. Otherwise I'll look at creating a ticket.
Thanks for you quick responses
Thanks for you quick responses
PHi Cloudflare community, hope you are all great!
I have an issue when I import S3 from aws-sdk in an API route with NextJS. I can import types from "aws-sdk/clients/s3" but as soon as I import the S3 class from the same path, I can't build the project and get the error "Failed to collect page data for /api/stage"
I have an issue when I import S3 from aws-sdk in an API route with NextJS. I can import types from "aws-sdk/clients/s3" but as soon as I import the S3 class from the same path, I can't build the project and get the error "Failed to collect page data for /api/stage"
PHave any of you experienced this problem with S3?
PSorry, I realized the issue was with Nextjs and not next on pages. The solution was to use "@aws-sdk/client-s3" package instead of "aws-sdk"
EHi, I've been stuck for a few days on a pages issue because the bundle has exceeded 25MB using next on pages. I'm not an expert, but it seems like the bundling gets bigger the more dynamic routes you have which is something that is pretty much required for most serious websites.
Has anyone found workarounds to this or ways to limit the bundle size? I don't know what to do to make the bundle smaller and if I can't (or the limit can't be increased) I'm kind of stuck and would have to migrate...
Also hi to all my old cloudflare friends! Happy birthday week
Has anyone found workarounds to this or ways to limit the bundle size? I don't know what to do to make the bundle smaller and if I can't (or the limit can't be increased) I'm kind of stuck and would have to migrate...
Also hi to all my old cloudflare friends! Happy birthday week
BDo you use vercel/otel or any package that rely on it? (E.G., Sentry). If so, check this out: next-on-pages
FHi! Has anyone figured out how to use domain names on another provider with pages ? Without transferring domain
THello, @James just an update. I did open an issue with radix. Here is the link https://github.com/radix-ui/themes/issues/595 will let you know when it is fixed.
GitHub
When I tried to use Radix theme with Next.js and Cloudflare pages, during the build process I got this error Failed to compile. ./node_modules/@radix-ui/react-primitive/dist/index.mjs Attempted imp...
JI wonder if now that Cache-Tag is available for non-Ent there might be a better mechanism for storage
I guess unless tiered cache is enable on the zone (and not the default
I guess unless tiered cache is enable on the zone (and not the default
.pages.dev
Ecache tags being free doesnt change the behaviour where worker responses wont be cached unless they do it themselves with cache api
Ecache tags can be used alongside the cache api (put the cache tag on the response you feed to cache api) and that works, but it doesnt present any better options for cache storage
Jthanks Erisa – that makes sense! I guess I was imagining it as the worker itself (https://github.com/cloudflare/next-on-pages/blob/main/packages/next-on-pages/templates/cache/adaptor.ts) somehow leveraging Cloudflare Cache from fetch e.g.
but there are quite a few incorrect assumptions on there from my own mental model on Cloudflare Cache as you're pointing out AND how actually next-on-pages manages to make it work atm
fetch(somewhereInternal, { cf: { cacheEverything: true, cacheTags: [...] })but there are quite a few incorrect assumptions on there from my own mental model on Cloudflare Cache as you're pointing out AND how actually next-on-pages manages to make it work atm
Ethe blocker from fetch based caching working here is that a worker (or pages function) cant fetch itself in a way where the fetch cache works (it wont on service bindings for example, and those dont work w/ pages anyway) unless you get a weird setup where you host on one domain that then fetches another domain, which is a tad messy and not that easy to support as part of a framework (but i guess theoretically doable)
Jexport const SUSPENSE_CACHE_URL = 'INTERNAL_SUSPENSE_CACHE_HOSTNAME.local';brb signing up for this domain and putting it on Cloudflare as free zone
TAs for next-on-pages, is it possible to edge cache pages for non logged-in users?
AI updated my project and started noticing "Too many subrequests" errors in prod. I made a branch and did some testing, and found that this was caused by updating next from 14.1.0 to 14.2.13 - if I go back to 14.1.0 with the same code then this error doesn't happen. is cloudflare aware of any next change that would be causing this?
TQuestion for the crowd: what is the expect/your median CPU time? (Workers & Pages > project > Function metrics)
I'm curious if mine is high relatively speaking - it seems higher than Vercel but their usage dashboards are a bit difficult to use.
Also, has anyone managed to get
I'm curious if mine is high relatively speaking - it seems higher than Vercel but their usage dashboards are a bit difficult to use.
Also, has anyone managed to get
__NEXT_ON_PAGES__KV_SUSPENSE_CACHE
Aok actually it's weirder than this
Ai noticed that for some queries in my site, it is still getting that error, even on the older next version. (all queries do the same number of subrequests, and it is much lower than 50)
AI made a new branch at the commit I was at before today and deployed it.
Aand this new deploy, with the identical commit as a deploy from a few months ago, gets this "too many subrequests" error on some queries. the older deploy is fine
Aso 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/cloudflareIs 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? 
