My nextjs app is taking a long time to compile even sir small change is there any way to speed it up
My nextjs app is taking a long time to compile even sir small change is there any way to speed it up or it's my laptop problem
IDev mode or to compile for production?
MDev mode
ITry
next dev --turbo
Ihi i manage to deployed a nextjs ssr on cloudflare page with the plugin @Cloudflare/next-on-pages , issue is when i deploy , first i did it manual and took from .vercel/output/static , if i try to take the whole folder containing function deploy is failing
where do i deploy my functions folder then ? thank
where do i deploy my functions folder then ? thank
Jare you referring to the cloudflare functions directory? you should be using nextjs API routes instead if you use next-on-pages
Nnext-on-pagesBut if i check the files in the
__worker.js manually and gzip them they don't seem to be bigger than 1MB so theoretically they won't exceed the limit.Any ideas what i could be missing?
DHi, I have a question, I am using cloudflare pages to host my nextjs (ssr) application, it has localhost everything is ok, no errors, but after deploying a new version of the application on one of the pages it shows an error "Internal Server Error". It's not an application error, it's kind of like cloudflare, nothing interesting is recorded in the logs. Any ideas?
Whow do you know it isn't an application error?
Wit sounds like one
PHello, I have a Cloudflare Pages app using NextJS (Pages router) in SSR. I'm trying to implement a custom 404 page. I have created a 404.tsx file using getStaticProps but when I go to a non-existent page on Cloudflare, the page displayed is the nextjs _error component and not my custom 404. However it was properly generated as a static html file.
Apparently using SSR with Cloudflare Pages removes the default behavior to automatically return 404.html pages deployed. Indeed when running in node runtime in local the correct 404 page is displayed but when running in edge runtime with local workers (wrangler pages dev), I have the issue.
How could I implement this logic ?
Apparently using SSR with Cloudflare Pages removes the default behavior to automatically return 404.html pages deployed. Indeed when running in node runtime in local the correct 404 page is displayed but when running in edge runtime with local workers (wrangler pages dev), I have the issue.
How could I implement this logic ?
Manyone have an example of email workers on next-on-pages?
JDo you get any errors logged when using log stream or tailing the deployment?
SHey everyone, have others had issues hitting the 25 MiB individual file limit when using a mix of SSR and static pages?
Feel like there might be something missing in our config and everything is contributing to the bundle.
We've got DatoCMS as our data store and only a couple of thousand pages.
Feel like there might be something missing in our config and everything is contributing to the bundle.
We've got DatoCMS as our data store and only a couple of thousand pages.
IHard to see what is happening here when we don't see how the pages are generated in e.g. the next.js build output, willing to share a snippet of that?
Vi have an app where the user has access to a dashboard, makes some customisations that get pushed to a db, then if a user's customer goes to
myapp.com/the-users-name they will see a page that gets rendered based on the customisations applied. to do this in vercel i would use isr with revalidatePath(), since cf doesn't support it, do i just have to put export const runtime = 'edge' on the dynamic route and just have every request count towards the workers usage quota, correct?Jyes
Vight, thanks
FDoes anyone have recommendations for lightweight error logging SaaS products for next-on-pages? Adding Sentry doesn't seem to pass the Pages build
I@Firu I'm personally pushing logs and errors into Axiom, for front-end and back-end (https://axiom.co), it's not as feature-rich as Sentry but it does the job.
FI was looking at the same thing after my escapades in trying to get Sentry or Logpush to work. How's the integration experience? Could you please point me towards the docs you used?
Falso does it bloat for bundle size on deployment? Sentry adds 1.6Mb to all my frontend routes - which led to me going way past the upload size limit for a worker
HIt's pretty easy. You can just lob a JSON object at
https://api.axiom.co/v1/datasets/$DATASET_NAME/ingest with a Bearer tokenHnvm, just reread the convo
HYeah, just throw a JSON object like
Foh sweet, an HTTP endpoint
FFHNo, I do not(in fact, I don't use Next much anymore)
Fanymorewhat happened?
Falso 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/
