⚠️

重要前提

安装AI Skills的关键前提是：必须科学上网，且开启TUN模式，这一点至关重要，直接决定安装能否顺利完成，在此郑重提醒三遍：科学上网，科学上网，科学上网。查看完整安装教程 →

Cloudflare Workers迁移指南：从AWS Lambda、Vercel、Express快速迁移到边缘计算

workers-migration by secondsky/claude-skills

74 周安装量

105 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/secondsky/claude-skills --skill workers-migration

云服务开发运维性能优化

🇨🇳中文介绍

Workers 迁移指南

将现有应用程序从各种平台迁移到 Cloudflare Workers。

迁移决策树

What are you migrating from?
├── AWS Lambda
│   └── Node.js handler? → Lambda adapter pattern
│   └── Python? → Consider Python Workers
│   └── Container/custom runtime? → May need rewrite
├── Vercel/Next.js
│   └── API routes? → Minimal changes with adapter
│   └── Full Next.js app? → Use OpenNext adapter
│   └── Middleware? → Direct Workers equivalent
├── Express/Node.js
│   └── Simple API? → Hono (similar API)
│   └── Complex middleware? → Gradual migration
│   └── Heavy node: usage? → Compatibility layer
└── Other Edge (Deno Deploy, Fastly)
    └── Standard Web APIs? → Minimal changes
    └── Platform-specific? → Targeted rewrites

平台对比

功能	Workers	Lambda	Vercel	Express
冷启动	~0ms	100-500ms

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

错误	来源	原因	解决方案
`fs is not defined`	Lambda/Express	文件系统访问	使用 KV/R2 进行存储
`Buffer is not defined`	Node.js	Node.js 全局对象	从 `node:buffer` 导入
`process.env undefined`	所有平台	环境变量访问模式	使用 `env` 参数
`setTimeout not returning`	Lambda	异步模式	使用 `ctx.waitUntil()`
`require() not found`	Express	CommonJS	转换为 ESM 导入
`Exceeded CPU time`	所有平台	长时间计算	分块处理或使用 DO
`body already consumed`	Express	请求体	读取前先克隆
`Headers not iterable`	Lambda	Headers API	使用 Headers 构造函数
`crypto.randomBytes`	Node.js	Node crypto	使用 `crypto.getRandomValues`
`Cannot find module`	所有平台	缺少 polyfill	检查 Workers 兼容性

AWS Lambda 处理程序

// Before: AWS Lambda
export const handler = async (event, context) => {
  const body = JSON.parse(event.body);
  return {
    statusCode: 200,
    body: JSON.stringify({ message: 'Hello' }),
  };
};

// After: Cloudflare Workers
export default {
  async fetch(request: Request, env: Env): Promise<Response> {
    const body = await request.json();
    return Response.json({ message: 'Hello' });
  },
};

// Before: Express
app.use((req, res, next) => {
  if (!req.headers.authorization) {
    return res.status(401).json({ error: 'Unauthorized' });
  }
  next();
});

// After: Hono Middleware
app.use('*', async (c, next) => {
  if (!c.req.header('Authorization')) {
    return c.json({ error: 'Unauthorized' }, 401);
  }
  await next();
});

// Before: Node.js
const apiKey = process.env.API_KEY;

// After: Workers
export default {
  async fetch(request: Request, env: Env): Promise<Response> {
    const apiKey = env.API_KEY;
    // ...
  },
};

Workers 通过兼容性标志支持许多 Node.js API：

// wrangler.jsonc
{
  "compatibility_flags": ["nodejs_compat_v2"],
  "compatibility_date": "2024-12-01"
}

通过 nodejs_compat_v2 支持：

crypto (大多数方法)
buffer (Buffer 类)
util (promisify, types)
stream (Readable, Writable)
events (EventEmitter)
path (所有方法)
string_decoder
assert

不支持 (需要替代方案)：

fs → 使用 R2/KV
child_process → 不可用
cluster → 不适用
dgram → 不支持
net → 使用 fetch/WebSocket
tls → 由平台处理

何时加载参考文档

参考文档	加载时机
`references/lambda-migration.md`	迁移 AWS Lambda 函数时
`references/vercel-migration.md`	从 Vercel/Next.js 迁移时
`references/express-migration.md`	迁移 Express/Node.js 应用时
`references/node-compatibility.md`	遇到 Node.js API 兼容性问题时

分析依赖项：检查是否有不支持的 Node.js API
转换为 ESM：将 require() 替换为 import
更新环境变量访问：使用 env 参数替代 process.env
替换文件系统：使用 R2/KV 进行存储
处理异步任务：使用 ctx.waitUntil() 处理后台任务
本地测试：使用 wrangler dev 进行验证
性能测试：确保不超过 CPU 限制

workers-runtime-apis - Workers 中可用的 API
workers-performance - 优化技巧
cloudflare-worker-base - 基础 Workers 设置

🇺🇸English

Workers Migration Guide

Migrate existing applications to Cloudflare Workers from various platforms.

Migration Decision Tree

What are you migrating from?
├── AWS Lambda
│   └── Node.js handler? → Lambda adapter pattern
│   └── Python? → Consider Python Workers
│   └── Container/custom runtime? → May need rewrite
├── Vercel/Next.js
│   └── API routes? → Minimal changes with adapter
│   └── Full Next.js app? → Use OpenNext adapter
│   └── Middleware? → Direct Workers equivalent
├── Express/Node.js
│   └── Simple API? → Hono (similar API)
│   └── Complex middleware? → Gradual migration
│   └── Heavy node: usage? → Compatibility layer
└── Other Edge (Deno Deploy, Fastly)
    └── Standard Web APIs? → Minimal changes
    └── Platform-specific? → Targeted rewrites

Platform Comparison

Feature	Workers	Lambda	Vercel	Express
Cold Start	~0ms	100-500ms	10-100ms	N/A
CPU Limit	50ms/10ms	15 min	10s	None
Memory	128MB	10GB	1GB	System
Max Response	6MB (stream unlimited)	6MB	4.5MB	None
Global Edge	300+ PoPs	Regional	~20 PoPs	Manual
Node.js APIs	Partial	Full	Full	Full

Top 10 Migration Errors

Error	From	Cause	Solution
`fs is not defined`	Lambda/Express	File system access	Use KV/R2 for storage
`Buffer is not defined`	Node.js	Node.js globals	Import from `node:buffer`
`process.env undefined`	All	Env access pattern	Use `env` parameter

Quick Migration Patterns

AWS Lambda Handler

// Before: AWS Lambda
export const handler = async (event, context) => {
  const body = JSON.parse(event.body);
  return {
    statusCode: 200,
    body: JSON.stringify({ message: 'Hello' }),
  };
};

// After: Cloudflare Workers
export default {
  async fetch(request: Request, env: Env): Promise<Response> {
    const body = await request.json();
    return Response.json({ message: 'Hello' });
  },
};

Express Middleware

// Before: Express
app.use((req, res, next) => {
  if (!req.headers.authorization) {
    return res.status(401).json({ error: 'Unauthorized' });
  }
  next();
});

// After: Hono Middleware
app.use('*', async (c, next) => {
  if (!c.req.header('Authorization')) {
    return c.json({ error: 'Unauthorized' }, 401);
  }
  await next();
});

Environment Variables

// Before: Node.js
const apiKey = process.env.API_KEY;

// After: Workers
export default {
  async fetch(request: Request, env: Env): Promise<Response> {
    const apiKey = env.API_KEY;
    // ...
  },
};

Node.js Compatibility

Workers support many Node.js APIs via compatibility flags:

// wrangler.jsonc
{
  "compatibility_flags": ["nodejs_compat_v2"],
  "compatibility_date": "2024-12-01"
}

Supported with nodejs_compat_v2:

crypto (most methods)
buffer (Buffer class)
util (promisify, types)
stream (Readable, Writable)
events (EventEmitter)
path (all methods)
string_decoder
assert

Not Supported (need alternatives):

fs → Use R2/KV
child_process → Not possible
cluster → Not applicable
dgram → Not supported
net → Use fetch/WebSocket
tls → Handled by platform

When to Load References

Reference	Load When
`references/lambda-migration.md`	Migrating AWS Lambda functions
`references/vercel-migration.md`	Migrating from Vercel/Next.js
`references/express-migration.md`	Migrating Express/Node.js apps
`references/node-compatibility.md`	Node.js API compatibility issues

Migration Checklist

Analyze Dependencies : Check for unsupported Node.js APIs
Convert to ESM : Replace require() with import
Update Env Access : Use env parameter instead of process.env
Replace File System : Use R2/KV for storage
Handle Async : Use ctx.waitUntil() for background tasks
Test Locally : Verify with wrangler dev
Performance Test : Ensure CPU limits aren't exceeded

Cloudflare Workers迁移指南：从AWS Lambda、Vercel、Express快速迁移到边缘计算

🇨🇳中文介绍

Workers 迁移指南

迁移决策树

平台对比

相关 Skills

十大迁移错误

快速迁移模式

AWS Lambda 处理程序

Express 中间件

环境变量

Node.js 兼容性