I did, it is working. I am using prisma in both. I prefer prisma, but I think maybe I should use dri
I did, it is working. I am using prisma in both. I prefer prisma, but I think maybe I should use drizzle.
PSimple example that works
FIf I use neon, this works.
PDoes any one know can I ignore package-lock.json in deploy ci/cd github via cloudflare? Always when I add new library CI/CD fail, i need to build pages on cloudflare to make it work, and that takes time...
Por how to restart cloudflare page? I added new envs, and to make them work i need to restart app. How to do that? I discovered only one option: Retry deployment. Is there better way to do that?
JI've always suspected (but never investigated) that this may be due to the page being pre-rendered and Next.js is trying to invoke an action that the route's function doesn't have, but I haven't looked into it, nor do I plan to.
On the Next.js 14 front, if it works it works, but it's not been tested with Next.js 14 by the maintainers so YMMV.
On the Next.js 14 front, if it works it works, but it's not been tested with Next.js 14 by the maintainers so YMMV.
JWe don't generate source maps compatible with the next-on-pages output IIRC, and it wouldn't be very simple to do so IMO. The .next directory in the Next.js build directory. The .vercel directory is the Vercel CLI build directory, and .vercel/output/static/_worker.js is the output directory for next-on-pages.
Jre-deploying
SHas anyone managed to get Sentry working with next-on-pages? It works perfectly locally but as soon as it's deployed to Cloudflare pages we get zero events in Sentry. It's almost like there's a network issue between Cloudflare and Sentry. Nothing in the logs at all. The test error in the route handler is logged as a 500 in the Cloudflare log stream but that's it.
I@Sam already found a solution? Sounds like Sentry is not enabled in production, possibly due to it not finding the environment variable NEXT_PULBIC_SENTRY_DNS for example. You need to make sure this is available at runtime (in your wrangler.toml or in the dashboard) for potentially SSR and during build time for e.g. static pages (e.g. in your Github CI/CD)
WIs this an OK room to ask questions about opennextjs as well? I dont see a room for it
VThere is a dedicated OpenNext Discord, check opennext.js.org
Wah! thank you
Jthat route uses server functionality and would need to be opted into the edge runtime for next-on-pages
IThe error message you quoted should have the solution right in it.
IIs there a reason you can't use edge config for that? It's required, because the client can't get the headers at all (they're a server-side thing).
IDoes one of the packages you are using use async_hooks?
Jcan you post the full build log please
JPlease can you update to use the latest version of the CLI - I believe your issue might have been fixed in v1.13.6. I will note that your compatibility date will need updating to a date after after Sept 23rd 2024 as well.
Mhiya, im desperately trying to understand how to use drizzle, hyperdrive and nextjs on edge but i swear im not getting past the env.HYPERDRIVE.connectionString step 
has anyone dealt with some like this before?
has anyone dealt with some like this before?
VI have added runtime = 'edge' on a page, but the CF still complaining that
runtime:edge
VAny suggestion? or the
/pages
Dtry adding it in the layout too
Von root layout?
Dyeah
VNo, again same error
VRenamed “/pages” directory to “/links” and it worked. So it seems CF build script has some bug.
I need to keep the “/pages/[id].tsx” route, so will wait for someone response for a bug fix.
I need to keep the “/pages/[id].tsx” route, so will wait for someone response for a bug fix.
Wis the "use client" at the top is overriding the edge runtime?
WIn the middle of a few things so a bit delayed atm
error is
error is
Error 8000022: Invalid KV namespace ID (homepage-nonces). Not a valid hex string. Check your KV namespace ID and try again.
Wyou need the namespace id (hex string) not the name
HHello, On my localhost I go to my dynamic root for my projects, this works. However if I try to load that same page on my worker page it gives me a Internal Server Error 500? The building and deploying works fine but if I just go to that page it gives me the 500.
It worked 4 months ago but now I pushed an update it doens't anymore?
My cloudflare logs give this:
It worked 4 months ago but now I pushed an update it doens't anymore?
My cloudflare logs give this:
Jit sounds like Next.js did. It probably thought that pages meant the pages directory and built your app wrong before we got the build output
Jupdate to latest version of next on pages and bump your compatibility date
GI am getting the
This error gets thrown when I call the native
XMLHttpRequest is not definedThis error gets thrown when I call the native
fetch
Gi am using latest version
1.13.7has anyone experienced this?
Ga lot of people suggest to downgrade to an older version, but then I get the async_hooks error
SNope, not fixed it. We're setting 
It's weird that we're seeing some errors and not others. We've not quota or anything. I'm talking with Sentry support at the moment on it. Hopefully we can work it out.
dsn
VSo, what can I change to make it work? My app needs the /pages routes should work.
Also the local build is working fine -
Also the local build is working fine -
V
HI upgraded to Nextjs 15 and now i get this error about my Nodejs on cloudflare being out of date:
How would i upgrade this version?
How would i upgrade this version?
INode is how some of the back-end / CLI javascript is run, to upgrade this it depends on your operating system, node has on their website nice steps you can follow to download / upgrade: https://nodejs.org/en/download
DThey probably want to upgrade the cloudflare version
DCreate a
.node-version22.12.0i did it with a env var in cloudflare,
this error comes up instead now
this error comes up instead now
HI changed from nextjs 15 canary to 15.1.4 and now i still get this error?
Hah wait nvm, i forgot compatibility date..
Hworks now
AI created a route to generate several static pages from the "domain" parameter, so I used "generateStaticParams".
I already received an error saying that I cannot use "generateStaticParams" together with "export const runtime = 'edge';"
but if I remove the "export const runtime = 'edge';" I get an error saying that I need to put it in the dynamic routes.
How should I solve this dilemma?
I already received an error saying that I cannot use "generateStaticParams" together with "export const runtime = 'edge';"
but if I remove the "export const runtime = 'edge';" I get an error saying that I need to put it in the dynamic routes.
How should I solve this dilemma?
AGitHub
next-on-pages environment related information System: Platform: linux Arch: x64 Shell: /bin/bash Package Manager Used: npm (10.7.0) Relevant Packages: @cloudflare/next-on-pages: 1.12.1 verc...