any luck with this? I'm getting this trying to run prisma & the neon driver
any luck with this? I'm getting this trying to run prisma & the neon driver
MI believe potentially due to using a singleton pattern for the prisma connection, is there an example I can look at on how to use neon & prisma in a CF worker
CThe right way of using prisma is by installing drizzle (https://orm.drizzle.team/docs/get-started-postgresql#usage-with-cloudflare-workers)
Drizzle ORM is a lightweight and performant TypeScript ORM with developer experience in mind.
PHello! I’m about to try this, but does this setup https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/ allows next ssr functionality? In other words, is this can replace Vercel completely? Thank you
Cloudflare Docs
Deploy a full-stack Next.js site (recommended).
JYes you can have SSR if you opt a route into the edge runtime
MI am trying to deploy nextjs 12 on CF. but said to add edge runtime to SSG or ISR pages like first image. I export the edge runtime as like 2nd pic but after that CF says that same error. The last image is the build config. How can I solve the error?
Mand my nextjs version is 12.1.0
PHas anyone got Sentry logging (server + client) up and running with Next on Pages using the App router?
PDoesnt seem to work if I follow the sentry install wizard of their next plugin
PI also have another issue with next-on-pages where sometimes the revalidateTag in a server action is returning the error: "Error: Invariant: static generation store missing in revalidateTag X"
Ti have a question: is there any tool that can convert the code nextjs written in nodejs to cloudflare edge runtime (v8 engine) to deploy in cloudflare
JNot currently
I
Also curious about this, I wanna try out vercel's open telemetry package soon, for workers people use generally ToucanJs, a sentry compatible package, but it hasn't been updated in a while. I know a while ago there was some conversation in the sentry cliënt GitHub. Keep me posted if you find a nice solution, I'll look into this in the next coming weeks too!
PTry placing it at the very beginning of the file
PDoes —turbo flag apply for cloudflare next-on-pages ??
PAnother question, are the server actions functional with next-on-pages ? https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations
Learn how to handle form submissions and data mutations with Next.js.
Dyes they are 
PThat’s fnice
DGitHub
next-on-pages environment related information System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020 CPU...
DI need to investigate this 
PI’ll try in our test setup and let you know. Don’t worry even if there are minor bugs, it is solving a lot of problems for us. Keep up the good work
Dawesome! thanks! 
Dyeah please let me know, either here or by opening issues in the gh repo
PDo you think this setup is similar to next-on-pages in terms of performance results? https://youtu.be/ItGUt2DqNy4?si=8YqMvbv4U-xwJoRN
YouTubeJosh tried coding
Turns out a method i found out that seemed pretty hacky to me at first because it messes with framework defaults actually works quite well. It's pretty fast, cheap, and easy to set up. Honestly there might be bugs that I haven't found yet, so please dont use this in production yet lol
-- sources for this video
hono: https://hono.dev/
cloudflare...
-- sources for this video
hono: https://hono.dev/
cloudflare...
DI must admit that I haven't done any proper benchmarking but I think that using
next-on-pagesnext-on-pages basically generates a worker for you, which via lazy loading brings in and executes the minimum amount of code possible to handle a request, all done at the edge, so as long as Next.js is involved I don't think you can get much faster than using next-on-pages
Dnext-on-pages is not perfect and does have it's drawbacks and issues, but performance wise in theory it should be practically the most performant way to deploy a Next.js app
D(including the API routes of course)
PThat’s music to my ears 
THello there. Is the smart placement work on next-on-pages yet?
Jsmart placement is pretty broken with Pages in general at the moment
PHi Dario, could you elaborate on the existing drawbacks and issues? Just starting with next on pages and seems to run fine for us, but before making a switch from Vercel with big projects, want to know the ins-and-outs
TBut it still works well with Workers. Is it correct?. i am planning use next-on-pages for deploy my nextjs app and use CloudFlare Workers for API route with smart placement. what do you recommend about this setup?
TYou mean this is the Pages Functions?
Jwe've been adopting next-on-pages recently and it's been working really, really great (kudos to Dario/James/any other contributors I might be missing!)
(on a somewhat similar note to the messages above) I did want to know if either of you had any methods to reliably profile timings in Cloudflare workers – we were surprised to see that:
seemed to be reporting
(on a somewhat similar note to the messages above) I did want to know if either of you had any methods to reliably profile timings in Cloudflare workers – we were surprised to see that:
seemed to be reporting
XXX msXX msI'm not sure about workers because I don't use Workers, I just know that Smart Placement can cause internal errors with Pages. You can try your setup though, I'm not sure if it only happens with Pages functions or if it also happens with static assets
LI have a question. If we were to deploy a server side NextJS app to pages, is there a list of originating IP addresses that app would communicate with or a way to get a list of IPs from our deployment that can be whitelisted on another system we have?
JSomeone correct me if I'm wrong, but the IP's of outgoing requests from Workers ought to match Cloudflare's ips's https://cloudflare.com/ips but just because a request is coming from that IP doesn't mean it's legitimate traffic. There's some good info here https://news.ycombinator.com/item?id=26690388
This page is intended to be the definitive source of Cloudflare’s current IP ranges.
kentonv
Hi, I'm the tech lead of Cloudflare Workers.This article contains several misunderstandings.If a Cloudflare customer has configured their origin server to respond only to Cloudflare IPs, then they MUST also verify that the "Host" header on any request actually matches their domain name. If they do not verify the Host header, then anyone can sign...
Hacker News
•4/4/21, 3:47 PM
LIf that is the case, that is awesome. Will wait on any anti-confirmation.
Tthank you so much for the infor James
QJust found this. I've been deploying Next SSG to Pages for a hot minute now. Is this channel for SSR? I wasn't aware of Pages offering SSR. If so, is there any documentation about this?
HDYes, it's documented here https://developers.cloudflare.com/pages/framework-guides/nextjs/
(specifically for Next.js)
https://developers.cloudflare.com/pages/framework-guides/nextjs/(specifically for Next.js)
Cloudflare Docs
React framework for building full-stack web applications.
PHey, I’m trying to find a solution for hosting with next-on-pages a full slug translation i18n (ex: fr/blogue, en/blog). Looking for a solution without the use of a middleware like amannn/next-intl does, the only viable I found right now is svobik7/next-roots copying folders on build. Any other ideas or examples your guys are aware of? 3 days of searching now and It seems complicated..
JYou could maybe use next.config.js rewrites, but that could end up being pretty laborious
0hey guyss, anyone here has a nextjs 14 using drizzle and cloudflare d1 github repo that i can look at? just trying to see and learn how other people doing it
JHey guys, how might I troubleshoot an: "Error code: 1000" error for a next on pages project? It uses pages router, and the /api route throws status code 403, with a plaintext response of "error code: 1000". Works locally with wrangler pages dev. The logs do not make it to the log tail, so seems its before my app
JI see online that 1000 implies I'm pointing to a cloudflare ip in some way, but this is just a pages.dev/api/ route, so im not sure how
JIt seems that passing of specific
x-vercel-*cf-*next/headers
EIt was likely the cf-connecting-ip header
MHey, I've got a next-on-pages project, and I'm running into Error 1101 and the CF dashboard is showing:
How do I go about debugging this? As I can run this locally with
How do I go about debugging this? As I can run this locally with
npm run devnpx wrangler dev