```tsx 00:08:56.974 Detected the following tools from environment: bun@1.1.4, nodejs@18.17.1, npm
For 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=1 (testsome-url?test=2 I would get it for ~500 ms again. If I refresh any of those I would get it for ~20 ms. I would expect that the test=2 will be already very fast after the test=1 was already executed, because the testAny 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?
Ti prefer uploading from client after you get the presignedurl
Mnot sure what's happening but I'm deploying my site using next-on-pages on CF, it gives me a preview deployment url, but it actually fails to deploy when I check on CF's end
OI'm trying to get cache headers working for images loaded with custom loader which utilizes the default Cloudflare Image Optimization implementation. These files are served from the public folder (
I've tried to add the following config settings:
I also tried adding them to
Only way I've been able to get cache headers working for these files is by modifying
Am I missing something or is this the only way to get cache headers working for these images?
public/images) which by default gets no cache (public, max-age=0, must-revalidate) and so the optimizer serves them with this header as well.I've tried to add the following config settings:
I also tried adding them to
_headers file in the root of the project but they don't seem to get included in the final build.Only way I've been able to get cache headers working for these files is by modifying
./.vercel/output/static/_headers after the build by adding this to the end of the generated file:Am I missing something or is this the only way to get cache headers working for these images?
THey there 
I currently have a website on Vercel and the main reason we chose Vercel was due to how easy it was to set up a multi tenant system (we allow our "Pro" users to attach a domain to their profile and it's as simple as letting them point either a root domain to the Vercel IP, or a CNAME to their subdomain (username.website.com)).
I'd like for us to move back to Cloudflare tbh, as I have never been a big fan of Vercels pricing model (even before the recent changes), but I'm stuck at a loss of understanding how we could set something like this up on Cloudflare, as it's quite confusing regarding the "edge certs/client certs/custom hostnames/origin server etc.
Is there any documentation/posts/resources to help point me in the right direction? Right now the routing is just going through the middleware.ts and Vercel pretty much take care of the rest.
TIA!
I currently have a website on Vercel and the main reason we chose Vercel was due to how easy it was to set up a multi tenant system (we allow our "Pro" users to attach a domain to their profile and it's as simple as letting them point either a root domain to the Vercel IP, or a CNAME to their subdomain (username.website.com)).I'd like for us to move back to Cloudflare tbh, as I have never been a big fan of Vercels pricing model (even before the recent changes), but I'm stuck at a loss of understanding how we could set something like this up on Cloudflare, as it's quite confusing regarding the "edge certs/client certs/custom hostnames/origin server etc.
Is there any documentation/posts/resources to help point me in the right direction? Right now the routing is just going through the middleware.ts and Vercel pretty much take care of the rest.
TIA!
NI believe all you need is a CNAME pointed to your pages subdomain and adding the domain in the project's settings
NYou can add it using the API too
NThere's a limit of 500 I believe, and no wildcard support yet
NYou could get around that using a worker to proxy it
TThanks, will investigate! I assumed I'd need to sort out the whole cloudflare for saas and all this complicated stuff
Bi have connection timeouts with no logs
BBon next 14.2
@Does anyone here know if No Access will be supported with next-on-pages? Recommend https://developers.cloudflare.com/workers/runtime-apis/bindings/rate-limit/ is updated to indicated rate limiting isn't currently working with pages. It works locally for me but fails on deploy, have been informed via ^rate limiting beta channel it's due to the way .toml is handled and there is no rate limiting setting within page settings
Mhaving this issue too randomly after hot reloading.
FIs Vercel dropping support for Edge rendering going to affect next-on-pages?
https://twitter.com/leeerob/status/1780705942734331983
https://twitter.com/leeerob/status/1780705942734331983
So, @vercel reverted all edge rendering back to Node.js 
Wanted to correct the record here as it's something I've advocated for in the past, and share what I've learned since then.
Also, the "edge" naming has been a bit confusing, so let's clear that up here as well.
What is…
Wanted to correct the record here as it's something I've advocated for in the past, and share what I've learned since then.
Also, the "edge" naming has been a bit confusing, so let's clear that up here as well.
What is…
4/17/24, 9:12 PM
ISo just keep in mind that this is for vercel.com, not all Vercel sites (which still can and do use edge rendering).
IThat doesn't mean it won't affect next-on-pages, but just to clarify that tweet.
I@fredkisss @vercel This is about Vercel’s usage of Vercel itself. Not your own site code 
4/17/24, 9:31 PM
FOh, I totally misinterpreted that tweet 
Thanks!
Thanks!
KHey guys, I am struggling with 'jose' for JWT signing and verification of tokens. I am writing a Next.JS app for cloudlfare pages, previously I had it statically generated and used Cloudflare's functions as the backend, but since I switched to next-on-pages, the cloudflare functions stopped working, so I had to refactor the entire "backend" to use Next.js API routes instead. The problem here is that once I switched to Next.JS API routes, I had to refactor the cloudflare functions middleware (which was responsible for authorization) into Next.JS API middleware, now after I did that the previously used library: @tsndr/cloudflare-worker-jwt stopped working, so I had to find a new one. The alternative that I found was 'jose' https://www.npmjs.com/package/jose. This is how I am using it to sign and verify a JWT:
Singing:
///////////
const JWT_SECRET = env.JWT_SECRET
const secret = new TextEncoder().encode(JWT_SECRET)
const alg = 'HS256'
const token = await new jose.SignJWT({
id: _id
})
.setProtectedHeader({ alg })
.setIssuedAt()
.setIssuer('urn:test')
.setAudience('urn:test-audience)
.setExpirationTime('15m')
.sign(secret)
Verifying:
///////////
await jose.jwtVerify(token, secret, {
issuer: 'urn:test',
audience: 'urn:test-audience',
})
The token and secret used in the verifying step are the same as in the signing.
The problem I have here is that the verifying fails with this message:
[JWSInvalid: Invalid Compact JWS] {
code: 'ERR_JWS_INVALID',
name: 'JWSInvalid'
}
Even though I try to verify the token immediately after I create it (I try this for debugging purposes).
If someone encountered a similar issue and can help me, I will be very grateful. Thank you and sorry for the long post.
Singing:
///////////
const JWT_SECRET = env.JWT_SECRET
const secret = new TextEncoder().encode(JWT_SECRET)
const alg = 'HS256'
const token = await new jose.SignJWT({
id: _id
})
.setProtectedHeader({ alg })
.setIssuedAt()
.setIssuer('urn:test')
.setAudience('urn:test-audience)
.setExpirationTime('15m')
.sign(secret)
Verifying:
///////////
await jose.jwtVerify(token, secret, {
issuer: 'urn:test',
audience: 'urn:test-audience',
})
The token and secret used in the verifying step are the same as in the signing.
The problem I have here is that the verifying fails with this message:
[JWSInvalid: Invalid Compact JWS] {
code: 'ERR_JWS_INVALID',
name: 'JWSInvalid'
}
Even though I try to verify the token immediately after I create it (I try this for debugging purposes).
If someone encountered a similar issue and can help me, I will be very grateful. Thank you and sorry for the long post.
