also update on Axiom, works very well so far without bloating the bundle. i love the non-opinionated
also update on Axiom, works very well so far without bloating the bundle. i love the non-opinionated nature of it
HNo real issues with Next, I just haven't used it in a while. Last I used it for my blog, which is now on Astro
FHow's the Astro experience on Cloudflare Pages? anything particular pain points or is it smooth so far? it looks pretty promising
IQuite smooth from my experience + what I've seen around here. Depends on what you're doing of course, but overall it seems pretty good.
ILikewise, a small little tip, I've two different loggers, one for server components / ssr / middleware and one (using a hook) for client components.
The reason I do this is that I can add more context to the logs this way based on which context we are, here's rough examples:
Probably smarter ways to do this but this has worked pretty well!
The reason I do this is that I can add more context to the logs this way based on which context we are, here's rough examples:
Probably smarter ways to do this but this has worked pretty well!
message.txt3.26KB
Fthis makes sense, definitely think it's a good idea to split the logs based on context
Fthanks for the advice!
DFirst time using Pages with Next.js, I was wondering if I can retrieve data from D1 directly from a Server Component, so that I can display that data on the page without needing to make an API call to another worker
KIs there a Cloudflare equivalent to Cloudinary's remote image fetch? And is there any good documentation on using it with Next's Image component?
SCloudflare Docs
Image transformations can be used automatically with the Next.js <Image /> component.
SHey, I think this happened before for some people and I'm not the first one. I have a page with a custom header component which fetches a external service and I seted to revalidate cache in 3 mins, but the page is building as static page. The header component is used on every page and if I put the runtime edge in root layout all the pages aren't anymore static rendereded.
SExample of function created:
SHow I could achieve that only that part of header is updated and rest remain static?
SDid you setup the cloudflare package on Next config?
SThe page where you use server actions, what render method it use?
SThat's on development env?
SI would check all steps from here: https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/get-started/
SYeah, and that client component is used on a page after all
SIn my case I was using a server action in header and it wasn't executed because it was static rendered and not on edge runtime.
SFunny thing to change all pages to edge runtime.
Dguys I'm using Next.js and want to use cloudflare pages with Puppeteer, which I'm assuming would run on workers instead of lambda functions, do you know a newer tutorial for Next.js, this one seems old:
https://blog.cloudflare.com/running-serverless-puppeteer-workers-durable-objects
https://blog.cloudflare.com/running-serverless-puppeteer-workers-durable-objects
FHi, I was trying to add observability to our pages project, but I was also encountering an unreasonable bloat up of the bundle size. Using vercel/otel package as alternative also does not work due to another open issue. I opened a new issue regarding this, as I would really like to understand what is going on
https://github.com/cloudflare/next-on-pages/issues/860
https://github.com/cloudflare/next-on-pages/issues/860
GitHub
next-on-pages environment related information System: Platform: darwin CPU: arm64 Apple M3 Pro Memory: 18 GB Shell: /bin/zsh Package Manager Used: npm (10.5.0) Relevant Packages: @cloudflare/next-o...
FIf you're ok with using another platform for o11y, I recommend Axiom
Fthey don't bloat the bundles
FThanks, looks great, will definitely give it a go
Fsure thing! lemme know if you find any pitfalls or pain points i might've missed
IAxiom actually also supports a lot of the OpenTelemetry standard, I also haven't got vercel/otel to work yet, if someone did, that would be awesome so I can send those into axiom too. 
SSure, been on other things the last few days.
job-logs.txt284.59KB
NgetRequestContext doesn't seem to have hyperdrive?
Nit smissing
Nand when it starts
NFound a non-empty WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING variable for binding. Hyperdrive will connect to this database during local development.
Hi deploy monorepo to pages and successful,but the access path is not available
Do you guys know the reason why
Do you guys know the reason why
Hthe monorepo is about next
MI‘m using Next Requests and next-on-pages.
Which IP is used when calling an external (free+publicly available) API?
I assume it’s Cloudflare‘s IP, isn’t it?
I‘m asking because I‘m afraid of hitting the rate limit of that external API.
Which IP is used when calling an external (free+publicly available) API?
I assume it’s Cloudflare‘s IP, isn’t it?
I‘m asking because I‘m afraid of hitting the rate limit of that external API.
Dwell, yeah, the request is sent from Cloudflare servers
Dit shouldn't be always the same tho, as it depends on the region and the server
SIs there any way that we can use single .env file for environment variables instead of duplicated variables in .env, .dev.vars, and the wrangler.toml file?
Junfortunately wrangler refuses to respect the industry standard of using .env
BHi, trying to create a Nextjs project with "npm install --save-dev @Cloudflare/next-on-pages" results in 5 vulnerabilities (1 low, 2 moderate, 2 high), running npm audit fix does not solve the problem. Any ideas?
Wmy d1 is not working on local machine, gives me error of table not found, using with pages, and d1 binding
I also gave it this value in wrangler.toml but doesnt seem to be working
I also gave it this value in wrangler.toml but doesnt seem to be working
Wcan anyone help me setup locally, just give me couple of steps
Dmight be obvious but... did you create the table locally?
Dafaik local database doesn't inherit anything from the real one
Wwhy to create local one? what I want to test the remote d1 on local ?
HWdaaamn, was this supposed to be a feature ? why ?
SI think I've figured out what's helping our next on pages worker bundle go over 25MiB.
We have 1256 static pages and 24 edge function routes.
The static routes are all output to a prerender-manifest.json (this is normal NextJS behaviour).
The next-on-pages deploy process copies the contents of this file into each edge function js file as a __PRERENDER_MANIFEST variable.
Our prerender-manifest.json comes in at 781KiB, so for me we've got it duplicated 24 times and in theory only need 1 copy of this in the final worker that's generated.
Has anyone else come across this before I raise it as a bug/improvement on GitHub?
We have 1256 static pages and 24 edge function routes.
The static routes are all output to a prerender-manifest.json (this is normal NextJS behaviour).
The next-on-pages deploy process copies the contents of this file into each edge function js file as a __PRERENDER_MANIFEST variable.
Our prerender-manifest.json comes in at 781KiB, so for me we've got it duplicated 24 times and in theory only need 1 copy of this in the final worker that's generated.
Has anyone else come across this before I raise it as a bug/improvement on GitHub?