Nthats the response text*
HNi never do anything with json there tho...
HIIRC you can downgrade
wranglerbruh moment
Ndowngrade?
Nin worker or page?
Nworker
HBoth maybe? Tbh, I'm still not quite sure what the problem is, but there is an issue for it: https://github.com/cloudflare/workers-sdk/issues/5620
GitHub
Which Cloudflare product(s) does this pertain to? Wrangler core What version(s) of the tool(s) are you using? wrangler@3.50.0 What version of Node are you using? 20 What operating system and versio...
Ndang it always seems to return 204
Nah nvm im a moron
Nshould be simple fix
Nhell yeah
Ntime to wrap it in some helper function and have locks in critical code
JHi, I can't deploy dynamic pages using next-on-pages. Any idea why?
https://github.com/cloudflare/next-on-pages/issues/745
Trying to bump the issue as I'm behind the schedule and the deadlines are evil. Y'll understand
https://github.com/cloudflare/next-on-pages/issues/745
Trying to bump the issue as I'm behind the schedule and the deadlines are evil. Y'll understand
GitHub
next-on-pages environment related information Relevant Packages: @cloudflare/next-on-pages: 1.11.0 vercel: N/A next: 14.1.4 Description I'm currently building a website with Next.js 14 and Pris...
NWhen deploying a NextJs site to Cloudflare Pages, are the pre-rendered pages still served via the worker/function, or are they served statically without triggering the worker on each request?
HThey are served by the Function. Next.js internally expects to handle every request for a page, unless you make the entire project static
NThanks for the clarification 
DIt will be very useful if next-on-pages logs the final functions size because most of the deployments are failing due to scripts size limits.
MFor some reason it's installing bun but then running npm install for me?
If I run it locally it uses bun as expected
FAbout Next.js' unstable_cache
Is it supposed to work out of the box?
My tests indicate that the cache works, but only as long as a given worker lives.
eg;
request A -> cache miss, puts the data in cache
request B -> cache hit, because it was handled by the same worker
request C -> cache miss, because it was handled by a different worker
I'm surprised to find nothing about unstable_cache in this Discord!
Besides this package, released 5 days ago
https://github.com/hansottowirtz/cloudflare-workers-cache
Is it supposed to work out of the box?
My tests indicate that the cache works, but only as long as a given worker lives.
eg;
request A -> cache miss, puts the data in cache
request B -> cache hit, because it was handled by the same worker
request C -> cache miss, because it was handled by a different worker
I'm surprised to find nothing about unstable_cache in this Discord!
Besides this package, released 5 days ago
https://github.com/hansottowirtz/cloudflare-workers-cache
Nmy page is randomly getting a 1101
N...
N"message": "The script will never generate a response.",
Non GET
Nfrom what i see so far all of these are for users on Edge?
Nmight be random
Nehh started happening again
Nchrome this time
Ndoesnt seem regional either
Nrare but happens
EThe documentation to get started with durable object it states i need to add binding in settings
Eexcept in the settings it refers me back to the documentation
EOk i found out you need te create a sepperate worker project
ETHEN you can bind it
GHey! I am using a CF worker as a caching layer to my NOP project.
So I am doing a
In my NOP pages I use SSR and I have
My problem is that whenever I request
Any ideas? Highly appreciated.
So I am doing a
fetchhttps://${url.hostname}/${language}/${country}/${deviceType}/${url.pathname}${url.search}In my NOP pages I use SSR and I have
fetchMy problem is that whenever I request
some-url?test=1testsome-url?test=2test=2test=1testAny ideas? Highly appreciated.
PHey, in a Next.js app running on Cloudflare Workers, what are the trade-offs between accessing a KV namespace directly using getRequestContext().env.MY_KV versus accessing it through a fetch request to the Cloudflare API, considering mostly performance? This api : https://developers.cloudflare.com/api/operations/workers-kv-namespace-read-the-metadata-for-a-key
Interact with Cloudflare's products and services via the Cloudflare API
HThere is also a rate limit on the API(I believe it is 1200 rpm)
Fgood point https://developers.cloudflare.com/fundamentals/api/reference/limits/
The global rate limit for the Cloudflare API is 1200 requests per five minutes per user, and applies cumulatively regardless of whether the request is made via the dashboard, API key, or API token.
[...]
Enterprise customers can also contact Cloudflare Support to raise the limit to a higher value.
HOh, five minutes, nvm
Cconsidering mostly performanceIf you're considering mostly performance, that api endpoint always goes back to core so it'll be way slower across the board. The KV binding uses cache in the local dc, and then goes to one of the central stores
Kmy CPU time on my next.js site hosted on cf pages seems high, is this normal? The functions aren't anything complex just the ones that run when initially loading the page. If your curious I had a massive traffic spike on the 15th
Manyone have server actions working with a deployed next app? not having any luck 
I'm getting a 405
I'm getting a 405MGitHub
next-on-pages environment related information System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020 CPU...
Mhowever when I add I then get a 404
Moh very strange... I had NODE_ENV = production, locally, so i could build using a .env for production before deploying to next ... removing that has it back to a 200 and working but I still need to provide on my static page unfortunately
Nyes, that is required
Nseem like a lot
NI have about 30-40ms
Nhow would one handle uploading files to R2 from a next.js server action?
