workers-help
pages-help
general-help
durable-objects
workers-and-pages-discussions
pages-discussions
wrangler
coding-help
kv
š¦rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
ā”instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd-runtime
web3
š¤turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows
vite-plugin
Migrating from Vercel, vercel.json alternative
Gitlab pipelines - "created by"
NextJS is slower on CF than on Vercel

Having trouble getting custom headers to work

Nuxt `npx nuxi generate` sometimes builds to `.output/public` and other times to `.dist`?
npx nuxi generate
and looking for the build dir of .output/public
. I've also tried with node 16 and 18 but it doesn't fix the issue.
Some branches are building, while others are not on CF. If I clone the branches with failed builds and run npx nuxi generate
locally it builds to the correct .output/public
dir. ...help me with this please
How to know when deployment was successful and is reachable?
Build error with simple ReactJS app on CF Pages

NextJS dynamic page with catch all route overrides all API routes
/pages/[...slug].tsx
). When trying to call any API route, it seems to route incorrectly to the catch all page instead of hitting the API endpoint.
I've tried doing local dev/builds and deployed to Vercel with the same codebase but haven't been able to reproduce it in all other circumstances, so it looks like it only affects @cloudflare/next-on-pages
builds.
Has anyone encountered this problem before?...Slow Cloudflare Pages

Page not displaying?

CloudFlare Pages Pointing to Domain from Different Account
Firebase for NextJS: "invalid key" when deploying on pages
c2cde2a643941234effc212d3922009f
...Error: Failed to publish assets.
Error: Failed to publish assets. For support, join our Discord (https://discord.gg/cloudflaredev) or create a ticket and reference the deployment ID: 17e127e9-3242-4017-bf03-2d9923221c19
Error: Failed to publish assets. For support, join our Discord (https://discord.gg/cloudflaredev) or create a ticket and reference the deployment ID: 17e127e9-3242-4017-bf03-2d9923221c19
Trouble uploading React app to cloudflare
Experiencing extremely slow load times
Internal error occurred when deploying
Exporting multiple functions in middleware plugins
Next on Pages with Next 14 suddenly produces huge build package.
npx @cloudflare/next-on-pages
produces a huge 45MB output and I get the Error: Failed to publish your Function. Got error: Your Functions script is over the 1 MiB size limit (workers.api.error.script_too_large)
Is this a known issue when switching to Next14, I'm aware it only came out a little bit ago. Or is this something more to do with my project?
Also while debugging and building using npx @Not Cloudflare :)/next-on-pages I keep getting asked to log into vercel, but that only happened after a few tries, what's up with that?...