Yea it's a KV namespace, I'm trying to show the use a message if something goes wrong is that not po
Yea 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.
WHey Folks- im trying to use KV/D1 inside a Server component, is this possible or only inside an API route? I can't find any examples online
I've got this in my next.config.js, but process.env.TESTKV is always undefined
I've got this in my next.config.js, but process.env.TESTKV is always undefined
WAnother question - is the wrangler.toml file not needed with next-on-pages?
Dim a n00b so don't quote me, but you should absolutely be able to access KV/D1 in a server component,
not sure why your setup is undefined, but i think you need to create a KV from local wrangler as well? could be totally wrong and/or maybe you already did this
in terms of
anyways others who are more knowledgable may be able to help more if you haven't already figured it out
not sure why your setup is undefined, but i think you need to create a KV from local wrangler as well? could be totally wrong and/or maybe you already did this
in terms of
wrangler.tomlanyways others who are more knowledgable may be able to help more if you haven't already figured it out
GitHub
Example/Demo app showing the usage of this new implementation: https://github.com/dario-piotrowicz/next-on-pages-next-dev-get-bindings-proxy-test-demo
fixes #623
fixes #634 (by shifting the issue ...
fixes #623
fixes #634 (by shifting the issue ...
Wthanks - maybe that is is my issue - I dont have the local one created. Is there any way to connect to the remote one while working locally?
Dusing just
you probably already saw this but the internal github doc:
that says it generates from miniflare, so i feel like you may not need it locally, but can't remember how i set it up last time hehe
next dev not that i know of but may be possible, im a huge donkey so hope im not leading you down the wrong direction, even now im wondering if i actually did create the KV in wrangler, or if it didn't just automatically do that,you probably already saw this but the internal github doc:
that says it generates from miniflare, so i feel like you may not need it locally, but can't remember how i set it up last time hehe
SI'm having some trouble with exceptions getting logged in Sentry and I think it is related to how Cloudflare Pages is bundling the application, but I'm not certain. basically if an error occurs locally, then it gets logged correctly as an exception to Sentry. but when deployed on Cloudflare Pages, it is getting logged as a console error message and not an exception.
we are still using NextJS 13 and the old version of next-on-pages
I tried adding a custom _error.js file like here but then it gave an error when building and said I need to specify that as an edge route, which I don't think is what I'm wanting to do?
we are still using NextJS 13 and the old version of next-on-pages
I tried adding a custom _error.js file like here but then it gave an error when building and said I need to specify that as an edge route, which I don't think is what I'm wanting to do?
JgetInitialProps can probably run on the server i imagine, so it will try to generate an node.js function I would assume. It's also a legacy API so your mileage may vary.
I don't know how sentry works, but the error it's logging could be the one that we catch and then log via console.error after running an edge function, but I'm not sure how sentry works so unsure if that's what's intercepting
I don't know how sentry works, but the error it's logging could be the one that we catch and then log via console.error after running an edge function, but I'm not sure how sentry works so unsure if that's what's intercepting
DHello, I'm new to cloudflare and want to contact with someone using cloudflare worker with next js application can anyone help me?! ~ty.
JCan you write your question please?
Sthe exceptions that should be getting logged are happening in the browser, but they seem to get swallowed up 
DMy question is Do we use next api routes If we're creating next js application with cloudflare or we are using workers?!
JYes you use next.js API routes if you want to deploy a full stack next.js app to cloudflare
JWould something like react-error-boundary help here perhaps?
