cloudflare-workers-frameworks_skill

Overview

This skill provides framework integration patterns and configuration for deploying modern web frameworks on Cloudflare Workers. It guides decisions for Hono, Remix, Next.js, Astro, SvelteKit, Qwik, and Nuxt, covering routing, SSR, static assets, bindings, and edge deployment. Use it to align framework choices, avoid common runtime errors, and follow best practices for production Workers apps.

How this skill works

The skill inspects framework-specific needs and produces targeted guidance: adapters, compatibility flags, and wrangler configuration for assets and bindings. It maps common runtime errors to concrete fixes (exports, globals, CJS→ESM, asset routing) and provides quick-start code snippets for Hono and static-asset fallbacks. It also recommends when to load deeper references for each framework and lists universal patterns for env access and error handling.

When to use it

• Starting a new Workers project and choosing a framework (React, Vue, Svelte, Qwik, Astro, Remix, Hono)
• Building server-side rendering or hybrid SSR/static sites on the edge
• Configuring static assets, D1/KV bindings, or Wrangler for edge deployment
• Troubleshooting runtime issues like globals, CJS imports, or asset 404s
• Optimizing bundle size, cold start behavior, or streaming SSR for Workers

Best practices

• Prefer Hono for APIs and tiny microservices; use adapters for full-stack frameworks when available
• Set nodejs_compat and appropriate compatibility_date for Node-like globals only when needed
• Keep top-level bundle small, avoid heavy initialization during cold start
• Serve static assets via the assets binding with a fallback to your app router
• Use streaming SSR and Cache API for large responses; implement universal error boundaries

Example use cases

• API-only service with D1 and KV using Hono and simple cors/logger middleware
• Remix or Next.js app on Workers using an adapter and explicit env/context passing for loaders
• Content site or blog built with Astro, hosted as static assets plus SSR pages
• SvelteKit or Nuxt app using Nitro/Open adapters with correct bindings and assets configuration
• Resumable Qwik app for instant interactions with minimized SSR work