does a request to one of my static pages count against my worker invocations?
does a request to one of my static pages count against my worker invocations?
HNope, you have to use Next’s API Routes
HYes, as next-on-pages requires itself to be run on all Pages, regardless of whether they are pre-rendered or not
H
Lalright
Lty
Lis it possible to use customer domains with next-on-pages, and if so, how do i do it? like if i want to allow people to register their own domains to be used for my multi-tenant nextjs project
Sman thats a bummer okay i guess i make a seperate repo
HNot sure I understand, why can’t you use Next’s own thing?
Sthe site's just already on next and I intend to migrate it away from next
SI want my serverside api to be seperate and with less overhead
UHi guys, hope all is doing great!
I want to host my nextjs app and was looking between Cloudflare and Netlify. The app contains dynamic pages and has a huge bandwidth. Is it possible to do so and what are the pros and cons of hosting on Cloudflare? I am asking only for Cloudflare since the website is currently hosted on Netlify and I am on the pro tier, but this is the refactored website that I want to deploy.
I want to host my nextjs app and was looking between Cloudflare and Netlify. The app contains dynamic pages and has a huge bandwidth. Is it possible to do so and what are the pros and cons of hosting on Cloudflare? I am asking only for Cloudflare since the website is currently hosted on Netlify and I am on the pro tier, but this is the refactored website that I want to deploy.
GHey, are server actions supported in next-on-pages? I'm getting the 405 method error, but the documentation states that it does support https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/supported-features/. Does anyone have a sample working code reference that I can review?
Also, is Next.js 14 supported? I see that Cloudflare only supports Next.js up to version 13 in online forums.
Also, is Next.js 14 supported? I see that Cloudflare only supports Next.js up to version 13 in online forums.
Cloudflare Docs
@cloudflare/next-on-pages supports all minor and patch version of Next.js 13 and 14. We regularly run manual and automated tests to ensure compatibility.
BAim
Upload my Next.js app's sourcemap file to highlight.io (or other services)
My attempt/Reproduction steps
Q1: What is the sourcemap file's path? I can't find it.
Q2: Do I need to make any changes in
Q3: Where can I learn more information about
Upload my Next.js app's sourcemap file to highlight.io (or other services)
My attempt/Reproduction steps
- I followed the official Cloudflare Pages docs (https://developers.cloudflare.com/workers/observability/source-maps/), and I added
upload_source_maps = trueto
file.wrangler.toml - My app's wrangler version:
"wrangler": "^3.99.0" - Run
pnpm next-on-pages && pnpm wrangler pages deploy
Q1: What is the sourcemap file's path? I can't find it.
Q2: Do I need to make any changes in
tsconfig.jsonQ3: Where can I learn more information about
.next/ and .vercel/ folders?
NI just added redirect rule but it does nothing
Neven did this in
dns
Ndoes nothing too, still does not redirect
Cwhat does this have to do with next on pages?
Na sorry thought it as
pages-discussions
FHello, can I use d1 with server actions?
Pyes, i am using it all the time
Pit works on nextjs 14, i am using it.
FI'm getting this error. In my other project, the PrismaD1 connection is exactly the same.
PTry with API and you will get answer if thats a problem with only server actions. I am using D1 with drizzle on server actions
FI 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 is missing on unable to build.
VAny suggestion? or the
/pages are some sort or reseverd name? as I have /contacts, /users and more pages which passed the build successfully
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.
