Deploying Next.js applications to Cloudflare Pages involves several challenges, including sparse documentation for the `@cloudflare/next-on-pages` package, confusion around using `wrangler pages dev` vs. `npm run dev`, inconsistencies with environment variables, and issues with HTTP response handling. The process also faces hiccups like a temporary SSL error on new projects. Despite the fast bug fixes, improvements in Cloudflare's developer tooling and ecosystem support are needed to match the smoother experience provided by Vercel.
Table of contents
Documentation for @cloudflare/next-on-pages is lackingwrangler pages dev is a bit confusing.dev.vars is inconsistent with .env.localA change in the vercel CLI broke @cloudflare/next-on-pages for everyoneSet-Cookie not working on a HTTP responsestatusText in HTTP response not being returnedERR_SSL_VERSION_OR_CIPHER_MISMATCH on new projectsNode.js Compatibility (Workers)Logging Experience1 Comment
Sort: