Dohhh okay thank you for the tip, will definitely zip to test, also do you know if we want to be under 5 or 10?
Ji think the limit was 25mb but i cant remember exactly
Dohhh wow, 25 would be amazing if thats the limit!
Dalso n00b Q: for sanitizing HTML does anyone have any recs on* for next-on-pages / workers? i tested a deploy of
sanitize-html and it happy path works, but in github, this user says it has issues: https://github.com/apostrophecms/sanitize-html/issues/639#issuecomment-1992159751, if anyone has a preferred lib super open to any suggestionsGitHub
The problem to solve Lots of console warnings are being logged since adding sanitize-html to a React application running with vite. This is details about the warning we are seeing. https://vitejs.d...
Jdompurify maybe?
VAnyone gotten this error before?
Vafter renaming some files/folder, it causes this when deploying
Verror doesnt occur when building or running localy
Vand dont have any build cache
Vright, git dosent track the folder name rename
VV
J
Dgood call, i can't remember why i didn't go with
dompurify, but definitely will give it a go if sanitize-html doesn't workout!
CDoes anyone have a working example of D1 + next-on-pages for both local dev and production?
Mwhat do you guys use for payment processing on C3 setup? stripe is giving a lot of failures in production worker env
JYou can use the next-dev sub-module for local development, and then you should be able to use the same binding from prod and dev via process.env.BINDING_NAME.
https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev
https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev
SHi guys, has anyone managed to deploy with react-email/tailwind? having error:
workers.api.error.script_too_largeJIf you're on the free plan, you might be hitting the 1mb limit. This can often happen due to chonky dependencies, or you just have a lot of SSR'd routes. You couly upgrade to Workers Paid for a higher limit
CHello Cloudflare community,
I'm encountering an intermittent error in my Next.js application deployed on Cloudflare Workers (next-on-pages). The error occurs in various environments and states:
The nature of the error:
Occurs sporadically
Doesn't consistently happen on the same user action
Sometimes occurs when the user signs out
Other times happens when navigating to a different route via side nav
What I've tried:
Reviewed code to ensure async operations are within handlers
Checked middleware and API routes for top-level async operations
Verified next.config.mjs setup for Cloudflare Workers
Ensured fetch calls in components are within useEffect hooks or event handlers
System info:
OS: Linux 6.5 Debian GNU/Linux 12 (bookworm)
Node: 22.4.0
npm: 10.8.1
pnpm: 9.5.0
Key npm packages:
@clerk/nextjs: ^5.1.5
@Cloudflare/next-on-pages: ^1.11.3
@Cloudflare/workers-types: ^4.20240605.0
next: ^14.2.4
react: ^18
react-dom: ^18
typescript: ^5
wrangler: ^3.60.2
Questions:
Are there known issues with Next.js on Cloudflare Workers causing this intermittent error?
Given the sporadic nature, what debugging strategies would you recommend?
Are there specific areas in a Next.js + Cloudflare Workers setup prone to causing this type of error?
Any insights or suggestions would be greatly appreciated. Thank you for your help!
I'm encountering an intermittent error in my Next.js application deployed on Cloudflare Workers (next-on-pages). The error occurs in various environments and states:
Error: Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope. To fix this error, perform this operation within a handler. https://developers.cloudflare.com/workers/runtime-apis/handlers/
Full stack trace varies depending on when the error occurred, but it typically involves files in the .vercel/output/static/_worker.js directory.The nature of the error:
Occurs sporadically
Doesn't consistently happen on the same user action
Sometimes occurs when the user signs out
Other times happens when navigating to a different route via side nav
What I've tried:
Reviewed code to ensure async operations are within handlers
Checked middleware and API routes for top-level async operations
Verified next.config.mjs setup for Cloudflare Workers
Ensured fetch calls in components are within useEffect hooks or event handlers
System info:
OS: Linux 6.5 Debian GNU/Linux 12 (bookworm)
Node: 22.4.0
npm: 10.8.1
pnpm: 9.5.0
Key npm packages:
@clerk/nextjs: ^5.1.5
@Cloudflare/next-on-pages: ^1.11.3
@Cloudflare/workers-types: ^4.20240605.0
next: ^14.2.4
react: ^18
react-dom: ^18
typescript: ^5
wrangler: ^3.60.2
Questions:
Are there known issues with Next.js on Cloudflare Workers causing this intermittent error?
Given the sporadic nature, what debugging strategies would you recommend?
Are there specific areas in a Next.js + Cloudflare Workers setup prone to causing this type of error?
Any insights or suggestions would be greatly appreciated. Thank you for your help!
WHowdy folks. I have a Next.js project on Cloudflare have have a
src/pages/api/signup.js api route that uses fetch to do a POST request to another app. When deploying it, the build failed and I needed to add the export const config = { runtime: 'experimental-edge' }; export to the api functionWThis seems to be breaking the function though.
req, res which are the parameters passed into the handler function don't work. The fetchmethod parameter I set and is still just doing a GETAny tips on debugging/fixing this?
Fit should be
export const runtime = 'edge'FAlso hey guys!
I got an issue using turborepo.
When building locally, it works fine, however when building on CF Pages, I get this:
I got an issue using turborepo.
When building locally, it works fine, however when building on CF Pages, I get this:
FWhere in my apps/db_web package.json, I have this script:
"pages:build": "npx @cloudflare/next-on-pages"F
WI tried “edge” but the build failed and said only “experimental-edge” or “nodejs” were valid runtimes 
FWhat nextjs version do you use?
WThis project was on 13.0.x but I then updated it to be on the exact version mention in the README in the next-on-pages repo.
Fso 14+?
FI don't know what version the repo says. But I am using the latest 14.2.5, and that works fine.
WInteresting. And do you happen to have api functions that use the fetch api to do a POST request? 
WI’ll try to upgrade the project to see if it works 
WThank you!
JWouldnt be able to tell without some sort of reproduction to play around with
JThat is not the format for edge api routes. You should consider using Next.js app directory route handlers instead as they function across both nodejs and edge runtime without needing changes, whereas the pages router has two different formats for edge vs nodejs
https://nextjs.org/docs/app/building-your-application/routing/route-handlers
https://nextjs.org/docs/app/building-your-application/routing/route-handlers
JLooks like something might not be configured correctly. Might be related to the wrong nodejs version. Might be that the package name is wrong. Not sure - I don't use turborepo
FHmm.. i'll try :/
Fstill broken :(
JI can only assume that turborepo isn't able to find a project with that name in your repo
FAh I found the issue! It seems that I forgot about changing the name in the package.json to @apps/db_web as well, so the filter actually works 
JHaha nice
ADavid Gomes
I recently went through the process of deploying various small Next.js applications to Cloudflare. As part of working on a new command called "neonctl create-app", we built a way to automatically deploy Next.js full-stack apps (i.e., Next.js apps with a backend+frontend) to both Cloudflare and
Ewhere can i put the _redirects file in a nextjs app? https://developers.cloudflare.com/pages/configuration/redirects/
Cloudflare Docs
To use redirects on Cloudflare Pages, declare your redirects in a plain text file called _redirects without a file extension, in the output folder of …
!did you solve the problem?
XI am unable to access the d1 database properly when running the CloudFlare Pages project locally using npm run preview,
I have added it to the wrangler.toml file
[[env.preview.d1_databases]]
binding = "DB" # available in your Worker on env.DB
database_name = "mydb_local"
database_id = "7926ce2e-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
But when using drizzle to access the database, it prompts that the table does not exist
I have added it to the wrangler.toml file
[[env.preview.d1_databases]]
binding = "DB" # available in your Worker on env.DB
database_name = "mydb_local"
database_id = "7926ce2e-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
But when using drizzle to access the database, it prompts that the table does not exist
