cloudflare-worker-base

Set up a production-ready Cloudflare Worker by scaffolding with `npm create cloudflare`, installing dependencies, configuring wrangler.jsonc with ES Module exports (export default app), and enabling Vite plugin for local development. This prevents export syntax errors and routing conflicts in production deployments.

Yes, static assets integrate with Cloudflare Workers through Vite and wrangler.jsonc configuration. Configure the assets directory and `run_worker_first` setting in wrangler.jsonc to serve frontend files alongside your Worker routing logic.

Implement SPA fallback handling in your Hono routing to gracefully serve index.html for client-side navigation requests. Proper SPA fallback configuration prevents routing conflicts between API endpoints and static asset requests.

Cloudflare Workers requires ES Module export patterns—specifically `export default app`—rather than CommonJS. This Skill's scaffolded structure enforces correct export syntax and prevents six documented deployment failures including upload races and legacy Service Worker format issues.

The Vite plugin enables fast HMR and local testing with Miniflare, improving development iteration speed. While optional, it's included in this production-ready baseline to prevent scheduled task failures and HMR-related issues during development.

Use a wrangler.jsonc template with explicit assets configuration and `run_worker_first` flag to ensure static assets load correctly and Worker logic executes predictably. This configuration prevents common deployment pitfalls documented in this Skill.