I use kysely personally, but your problem sounded similar to an issue I was trying to fix for someon
I 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=next (when creating a new project) or npx @cloudflare/next-on-pages on a existing project. Opens a wsl shell and is then frozen and when closed gives this error. I've already attempted to run the commands within WSL as suggested and the same shell still opens. Running without WSL enabled gives the other error. No other node processes are running, running the command as administrator does not work either.
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
N
JSeems 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
PThanks for answer. I would like to use SSG for /blog/* , but SSR for the rest 
Jah okay, in that case it will be fine as long as it's at build time
JDid you check out this page? https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/troubleshooting/
There are some other settings you might need to change due to how Nextjs generates dynamic routes
There are some other settings you might need to change due to how Nextjs generates dynamic routes
PThanks, added: export const dynamicParams = false . But same problem.
Kimport puppeteer from "@cloudflare/puppeteer";
can we use cloudeflare puppeteer inside nextj api route?
can we use cloudeflare puppeteer inside nextj api route?
Kor I'll just create a separate worker for it
PGo with separate worker 100%, you will have simple API to use it.
SHas anyone managed to get wildcard custom domains working with pages? I've tried using a proxy worker but I'm getting a 522 error. It works fine without the wildcard custom domain.
Se.g. *.example.com - mainly for SaaS stuff. https://developers.cloudflare.com/dns/manage-dns-records/reference/wildcard-dns-records/
SYeah, I need it to be wildcard for a SaaS product.
SYeah, they support it just not on pages for some reason. The workaround I've seen is to use a proxy worker (since you can use wildcard DNS there) but I get an error that makes little sense.
SYeah, I've seen that of course hence asking about the workaround or if anyone has got it working another way.
hence asking about the workaround or if anyone has got it working another way.Sa 522 error as above
SYeah, they're all pretty old which is why I figured I'd ask here
Sanyone know the answer to this? pages-helpHow can I access my d1 database in next on pages edge LOCALLY?
Jare you able to share some sort of repro by any chance?
Ndoes anyone know what could be the reason why a next/link in local dev mode doesn't cause a full page transition but deployed via next-on-pages it does?
Nweird it seems to transition fine when running with next dev but is doing the full page load if i try to run it with wrangler dev and the next-on-pages build output
JAre you able to share a reproduction?
NIs it possible that it's because the urls where it seems to full page load are " ● (SSG) prerendered as static HTML (uses getStaticProps)"?
I've noticed it seems to work fine on next on pages for the routes that are "ƒ (Dynamic) server-rendered on demand"
I've noticed it seems to work fine on next on pages for the routes that are "ƒ (Dynamic) server-rendered on demand"
