Migrating Pages CMS to vinext and Cloudflare Workers

[swalker326]

Summary

• migrate the app branch from Next.js conventions to vinext, including proxy/runtime wiring and catch-all editor/media routes for nested content paths
• adapt auth, database access, and cache helpers for Cloudflare Workers by creating DB clients lazily, centralizing base URL handling, and avoiding request-scoped sign-out side effects in Octokit
• add Cloudflare deployment and local database tooling with Wrangler, Hyperdrive-aware database setup, generated Worker types, and updated setup docs

Testing

• pnpm build
• pnpm lint (fails: ESLint 9 cannot find an eslint.config.* file in this repo)

[hunvreus]

I was actually investigating that to see if I could at least improve performance for dev. Main issue is that I'm finalizing a huge upgrade in the development branch (LOTS of changes, including upgrade to Next.js 16, update of all dependencies, new routes, perf improvements, bug fixes, UI updates...).

Two questions:

• Did you use the vinext skill to handle the migration?
• Were you able to run it on Cloudflare Workers (I was concerned that the bundle size would still be too much)?

[hunvreus]

2.0.0 is out. Feel free to give it a go. I may do it myself too.