!is there something wrong in the dependency?
!
SI got some time to test this today, if we add _routes.json file and exclude these static routes then _redirects works
0hey anyone knows how to solve this problem
Node.JS Compatibility Error
no nodejs_compat compatibility flag set
Node.JS Compatibility Error
no nodejs_compat compatibility flag set
JIn your Pages project, go to Settings > Functions > Compatibility Flags.
Configure a nodejs_compat flag for both production and preview.
Configure a nodejs_compat flag for both production and preview.
JIt does say this in the error page.
0added nodejs_compat
still showing same error
still showing same error
JRedeploy your project.
!I added necessary dependency to my next js project but still having errors with deployment on cloudflare, it's working well with GitHub pages
!If anyone can help personally then please reply i will send you the repo link
BCan you show what errors exactly you are getting
!!!Can you please checkout my project?
BIt shows pretty clearly the errors, just check them out one by one
!I tried every way but still, I'll be very thankful if you can help me by visiting my repo
Dn00b Q: updated
if i comment out this config portion dev server comes back:
super open to any suggestions or if there is doc don't hesitate to point it out!
next-on-pages and getting this:if i comment out this config portion dev server comes back:
super open to any suggestions or if there is doc don't hesitate to point it out!
JPlease can you try using it in this format:
Please can you also open an issue on the next-on-pages GitHub repo as it looks like the docs might need updating about the correct syntax.
Please can you also open an issue on the next-on-pages GitHub repo as it looks like the docs might need updating about the correct syntax.
Dohhhhh got it, this is awesome and it totally works! thank you!
also posted an issue and i believe i pinged you correctly, if i got the issue formatting wrong, don't hesitate to let me know!
also posted an issue and i believe i pinged you correctly, if i got the issue formatting wrong, don't hesitate to let me know!
JPerfect, glad to hear it worked!
JI set up my D1database like this and it's giving me an error
Jlooks like I had to do this instead to get it to work
Dsuper interesting that you removed
bindings and it works, possibly the API allows for bothJIs that on the latest next-on-pages version?
J1.8.5
Jsorry I left out some key stuff, this works.
BIs it possible to partly have local dev bindings and party remote dev bindings?
BLet's say, I want to use D1 locally, but R2 remotely during local development
JThe next-dev submodule uses miniflare and does local bindings, so im afraid not
3New to using Next.js, I'm running
next build.meta and .rsc files when building how can I disable non essential static site files like these? Also does Cloudflare Pages have an option for us to check what files are generated and distributed on their CDN after a build is finished?Jrsc files are essential
3Even 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' so I'm back to square one 3I will try and modify my build script to delete
*.txt files at the end and see how that goesDokay 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.com, blog on blog.mydomain.com, landing page on mydomain.comI 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
KV namespace, then it is valid behaviour that it returns void. It will throw an error if something goes wrongBYea 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?