cloudflare-to-bun_skill

Overview

This skill helps migrate Cloudflare Workers to Bun by providing runtime compatibility analysis, bindings replacements, and deployment guidance. It focuses on converting Cloudflare runtime APIs, mapping KV/R2/D1/Durable Objects to server-side alternatives, and adapting edge patterns to Bun server deployments. Use it when you need a clear, repeatable path from Workers to Bun-based servers.

How this skill works

The skill analyzes your worker type (service, module, scheduled, durable object, or pages function), inspects wrangler.toml and bindings, and maps Cloudflare APIs to Bun equivalents. It produces concrete code patterns for request/response handlers, routing (with Hono), scheduled jobs, and recommended replacements for KV, R2, and D1. It also provides configuration and deployment templates, environment variable migration, testing tips, and a migration checklist.

When to use it

• Converting a Cloudflare Worker (module or service) to a Bun server
• Replacing Cloudflare bindings (KV, R2, D1, Durable Objects) with Redis, S3, or SQL
• Moving from edge deployment to a self-hosted or cloud server setup
• Adapting scheduled Cron triggers and background tasks to Bun
• Preparing a migration plan that includes testing and deployment strategies

Best practices

• Start with a pre-migration analysis: verify wrangler.toml, worker type, and Bun installation
• Map bindings explicitly (KV→Redis, R2→S3, D1→Postgres/SQLite) and provision replacements before cutover
• Use a routing framework like Hono to replicate Worker route patterns and middleware
• Migrate environment variables into .env files and use process.env in runtime
• Containerize with Docker and include health checks and monitoring for server deployments

Example use cases

• Migrate an API built on Cloudflare Workers to Bun using Hono for routing and Redis for KV-like cache
• Convert a scheduled cleanup Worker into a Bun server job using node-cron and a Docker deployment
• Replace R2-backed asset serving with S3-compatible storage and the AWS SDK in Bun
• Move Durable Object stateful logic to a PostgreSQL-backed service with connection pooling
• Set up a local test flow: run Bun server, migrate tests from Miniflare to bun:test, and verify endpoints