Even for a static site? I don't mind missing out on prefetch. Would you recommend I go with somethin
Even for a static site? I don't mind missing out on prefetch. Would you recommend I go with something like Astro instead if this is the case?
3Upon closer inspection it seems
/out/ contains .txt files for each dynamic route page... not sure what these are but will investigate getting rid of them and my problem is fixed
Dnot sure if you are still around sir, but just wanted to say i started using this in dev and blown away how cool this is!
also curiously, how did you learn about the
also curiously, how did you learn about the
path setting in the config for the next image? the closest i see in the docs is remote patterns and loaders which seems the path - route handler is just in a cleaner/concise syntax if i am understanding it correctly, but if that is wrong would be super interested to learn more!
Jyes. the rsc file is needed for soft navigation. if nextjs cant get the rsc payload it needs, it will results in a hard refresh/navigation instead
DHere is the documentation (legacy):
https://nextjs.org/docs/pages/api-reference/components/image-legacy#loader-configuration
https://nextjs.org/docs/pages/api-reference/components/image-legacy#loader-configuration
Backwards compatible Image Optimization with the Legacy Image component.
DTo check the assets which were uploaded, you can navigate to deployment details > Assets Uploaded
Are you using output: "export" ?
Are you using output: "export" ?
3Yes, I'm using static exports for next.js... tried the assets uploaded tab initially but my browser will crash when loading 18k files but it did give me info about
.txtHowever it seems like i18n with Pages Router cannot 
output: 'export'I will try and modify my build script to delete
*.txtokay interesting, yeah i don't see a reference to that approach, but thinking it through more i guess the idea is if you understand the primitives (html img element + api routes), it just naturally follows that the pattern works, i just need to learn more hehe
LHey, is it possible to have a reverse proxy on cloudflare, so that I can merge a CF-hosted nextjs app with a hugo-generated static landing page and a hostinger-hosted blog, on different subdomains? (E.g. app on
app.mydomain.comblog.mydomain.commydomain.com
BI am trying to check if my request has been succesfull or errored but the return type is void, anyone know how to fix this?
HIf that is a
KVYea it's a KV namespace, I'm trying to show the use a message if something goes wrong is that not possible then?
HYou can use a
try/catch
BThank you, this seems to work
TNeed help with Next on pages prod deployment. I get 500 Internal Server Error when loading the page. The preview deployment works fine for some reason, its just the production deployment
JAre you using smart placement or log stream?
Tyes to smart placement, only look at real time logs occasionally for debugging, does that affect it?
Jdisable smart placement and try redeploying
Jit's caused internal server errors when enabling it with pages for months now
Tjust tried and seems to be working so far, thanks for the tip
Tany idea why it only happens on the production deployment?
Jbecause smart placement is broken with pages
Atrying to run it locally for development and getting this error
Ais it just the windows incompatibility?
JPlease can you open an issue in the GitHub for this
BIn production with this ssg generated page we get a ton of requests like this, anybody familiar with this?
BI believe it has something to do with caching, just not sure
JThat looks like Next.js' default prefetching behaviour when using the Next.js Link component. You can pass prefetch={false} I think it is to disable this behaviour.
J(assuming the comment was about all those requests happening when you visit one page and not just normal navigation around)
JThe RSC payload requests are for React Server Components to work properly on soft navigation between routes. The use a query parameter so that it plays friendly with CDNs that don't respect the
vary
BDamn didn't know, so does it prefetch the full route the link is going to?
JYeah if you use the Link component it will automatically prefetch the RSC payload for every link in the viewport (iirc), and that RSC payload will then be used when the link is clicked and cached in the browser tab for 5 mins i believe it is until refreshing (i think)
BThank you we are debugging our performance of the site, do you think this could have to do with it if there are a lot of these caching requests? On one particular page this goes op to 4000 requests
JWouldn't surprise me if the prefetching is killing your performance, because depending on what's on your page, it might have to do a serious amount of work and endless requests
JIf you are automatically prefetching more than 10 pages on load, that's too many IMO
BI'm going to test it out and let you know
BWell that drasticly improved holy
BBefore optimisation it was around 5 seconds
JBeautiful
NI am currently migrating my Next.js app to Cloudflare Pages. I have used SendGrids Web API to send emails (e.g. for my contact forms). That does not work after switching to the Edge runtime because SendGrid seems to use Axios to send their emails (as i found in my error message and analyzing the sub-dependencies). What is the go-to solution for such cases? Do I need to use SMTP relays or is there an easier solution?
Current error (after submitting a valid form to my edge runtime configured api endpoint):
Current error (after submitting a valid form to my edge runtime configured api endpoint):
Dnot sure if you've checked out resend, they have an edge compatible lib,
for what is considered best practice, i think if you want to stay on cloudflare stack maybe using mail channels since they have a partnership with CF but that involves adding a worker if i understand it correctly (which i may not)
for what is considered best practice, i think if you want to stay on cloudflare stack maybe using mail channels since they have a partnership with CF but that involves adding a worker if i understand it correctly (which i may not)
OHey i am using contentlayer and with nextjs and for this specific dynamic route, next-on-pages is asking me to make it run on edge but i get
if i use the default runtime locally, nothing goes wrong
if i use the default runtime locally, nothing goes wrong
Ois there any way i can bypass the runtime check? this dynamic route has a generate static params and will always only generate 3 different endpoints
JFor dynamic route SSG you need to tell Next.js to only generate the routes provided.
See how in https://github.com/cloudflare/next-on-pages/blob/main/packages%2Fnext-on-pages%2Fdocs%2Fgotchas.md
See how in https://github.com/cloudflare/next-on-pages/blob/main/packages%2Fnext-on-pages%2Fdocs%2Fgotchas.md
3Just wondering for edge runtime if we have dynamic routes (
Does this apply to static sites only or everything? My reason for doing this way is I have more than 20,000 pages (I'm forced to use edge runtime instead of static export) I plan to make the popular pages static so in theory it will reduce calling a worker functions. Would I have to also include these pages in
/blog/[slug]/blog/1Does this apply to static sites only or everything? My reason for doing this way is I have more than 20,000 pages (I'm forced to use edge runtime instead of static export) I plan to make the popular pages static so in theory it will reduce calling a worker functions. Would I have to also include these pages in
routes.json
KAs everything except
/_next/static/*
AAnyone get D1 working with local development? I've tried every blog post and looked through here and can't seem to figure it out. I would be happy with developing against the remote DB or local DB. Every time I'm in dev mode it seems to be connecting to an empty Sqlite DB that doesn't have any tables in it based on the errors. I've tried putting my remote DB name/ID in the bindings or a local one and i get the same results.
A(it works fine when deployed)
JThey will still invoke the worker as Kev said, unless they're in _routes.json. But excluding routes (instead of assets) from invoking the worker is generally not a good idea as non-static exports expect to be able to through a series of phases and rules for routing that Vercel defines for us.
There are still benefits to prerendering routes though, as it would reduce your final worker size, not need to spend cpu time to render the page, not need to make fetch calls during a render, and so on. So there are benefits still.
There are still benefits to prerendering routes though, as it would reduce your final worker size, not need to spend cpu time to render the page, not need to make fetch calls during a render, and so on. So there are benefits still.