Next.js on Cloudflare Pages
Pushed from GitHub, built with npm, exported to static HTML and served from Cloudflare's edge — with a Pages Function alongside it. Every platform feature below verifies itself in your browser.
Live checks
Next.js built this page to HTML and Pages served it.
Calling /api/hello …
Looking for x-pages-test …
Following /old-page …
Edge info
Waiting on /api/hello. This only resolves on a real Cloudflare deploy (or under wrangler pages dev) — plain next dev has no Functions runtime.
What this proves
npm packages build
Bootstrap 5 is a real dependency, compiled at build time. If the page is styled, npm install and next build both ran on Cloudflare.
Functions at the edge
functions/api/hello.js runs on the Workers runtime and reports which datacenter served you.
Routing & 404
App Router pages export to static HTML; not-found.js becomes the 404 page Pages serves.
Headers & redirects
public/_headers and public/_redirects ship in the build output and are applied by the CDN.
Try a redeploy
Change the headline in app/page.js, commit, push. Cloudflare rebuilds on every push to the production branch, and gives pull requests their own preview URL.
git commit -am "tweak headline"
git push