Not sure where to start to debug this tbh,I’m happy to help figure out what’s going on 👌
Not sure where to start to debug this tbh,I’m happy to help figure out what’s going on 
AIf I have trouble adding a new website to Cloudflare, where do I look for a solution?
A
A
I?crossposting
Jgetting an idea of which chunks are overly large could help. could grab the size of all files in the _worker.js dir and sort by size to get an idea of where we might have an issue
TI'm cross-posting here on behalf of @Lila Rest because I think this is more next-on-pages related than Hyperdrive related, hyperdrive
When you try to connect to a database using postgres-js (https://github.com/porsager/postgres) (even without Hyperdrive), you get errors such as:
Any insights here?
When you try to connect to a database using postgres-js (https://github.com/porsager/postgres) (even without Hyperdrive), you get errors such as:
Any insights here?
LThanks Thomas, I appreciate that 
LAnd my question is more generally to be able to make CF Pages, CF Hyperdrive and Prisma working together
YThis should help Does Smart Placement support Hyperdrive? I'm using Next.js with Postgres, do note that this won't work locally with next dev though
LInteresting, thanks for surfacing that thread!
Two things, though:
Two things, though:
- it seems that the author is encountering an issue with smart placement
- the author uses Drizzle and we're using Prisma
Any idea how to address these two?
YThe webpack config and sed trick is not specific about smart placement nor ORM, more about getting
cloudflare:socketsYeah I get that, then how to use Prisma instead of Postgres.js/Drizzle to query HyperDrive, or how to plug Postgres.js to work through Prisma? Have you seen someone trying that here?
YIn your case, after the trick you can use https://www.npmjs.com/package/@prisma/adapter-pg-worker to connect
npm
Prisma's driver adapter for "@prisma/pg-worker". Latest version: 5.19.1, last published: a day ago. Start using @prisma/adapter-pg-worker in your project by running
npm i @prisma/adapter-pg-worker
CHow to talk with support clourflare
H?support
FTo contact Cloudflare Support about an issue, please visit the Support Portal and fill in the form on the portal. After submission, you will receive confirmation over email.
Some issues, such as Account or Billing related issues, cannot be solved by the community.
Any plan level (including Free plans) can open tickets for Account, Billing or Registrar ticket categories. Make sure to select the correct category to ensure it goes to the right place.
For more information on the methods by which you can contact Support for your plan level, see Contacting Cloudflare Support - Cloudflare Docs
Some issues, such as Account or Billing related issues, cannot be solved by the community.
Any plan level (including Free plans) can open tickets for Account, Billing or Registrar ticket categories. Make sure to select the correct category to ensure it goes to the right place.
For more information on the methods by which you can contact Support for your plan level, see Contacting Cloudflare Support - Cloudflare Docs
LIs this extension working with Postgres.js or with
If
pgIf
pgcould you try out my comment from this discussion? https://github.com/vercel/next.js/discussions/50177#discussioncomment-9409065
GitHub
Summary Hi, I am a new developer trying to create a tool to visualize sql data tables, and to render and visualize the tables, I need a PostgreSQL URI so that i can connect to that database, but i ...
LI will thanks! Are you using Prisma then? Or another ORM?
JI use kysely personally, but your problem sounded similar to an issue I was trying to fix for someone else before
LYes there are two issues here, the Postgres.js error and being able to make Prisma work with else Postgres.js else Hyperdrive directly
SHas anyone used T3 Stack with next-on-pages? How the DX for using it?
PRunning into an issue when running
npm create cloudflare@latest my-next-app -- --framework=nextnpx @cloudflare/next-on-pages
Dyeah I reported this a while ago No Access
You can actually just ignore the error, that step isn't necessary and when running
You can actually just ignore the error, that step isn't necessary and when running
npm run dev
PWhich is what I'm wanting to do as I'm using D1 
DI'm using D1 too but in the development build everything works perfectly. Why do you need to test the production build locally too?
DI mean, it's surely something that needs to be fixed but it shouldn't be a big problem for most developers
P
NJSeems like Vercel CLI issue
NBut it works fine on other platforms. So, does CF pages have an older version of the vercel cli?
SCan somebody explain to me how the cache option works? I've set the binding according to docs: https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/caching/#workers-kv-recommended
- but I don't see any fetch() requests from SSR pages being cached in the KV. It's basically empty.
Cloudflare Docs
@cloudflare/next-on-pages 
supports caching and revalidating data returned by subrequests you make in your app by calling fetch().
supports caching and revalidating data returned by subrequests you make in your app by calling fetch().
JYou can specify a version in your package.json
AI'm trying to use functions directory for api routes in next.js but it's just sending 404 error for any route I create inside functions directory. I tried with other framework astro too. Getting same error.
AI tried on just a barebone hello world project created using cloudflare cli.
AWant to use functions directory because pages doesn't support node.js runtime on next.js api routes.
KHello
KDoes anyone tried nextjs-on-pages in a big projects? is it scalable?
KDoes the middleware in nextjs work with nextjs-on-pages?
KI have tried it but it seems not working, I implemented my own checking but in each api route so I think technically its not a middleware just a simple checking of each request
Jyou can't use the functions directory when using next-on-pages since we generate our own worker for your app, so you need to use next.js API routes.
Jyes
AOk. But next.js api routes doesn't support node.js runtime. So all the benefits of workers node_compat will be of no use and we can't use package like mongodb and firebase with that.
Jfunctions directory doesn't support nodejs either
KCloudflare Docs
If you need to run code before or after your Next.js application, create your own Worker entrypoint and forward requests to your Next.js application.
Jnextjs middleware runs on workers regardless of whether it's deployed to Vercel or cloudflare. Vercel use cloudflare workers for hosting nextjs middleware
PCan I use SSG (static site generation) on next-on-pages? I need that to create a blog. Not sure if SSR is good for that.
JIf you're using SSG you probably wouldn't need to use next-on-pages and could just do a fully static deployment instead