Imported from PP-Namias/Portfolio (.agents/skills/opennext-cloudflare/SKILL.md). Install upstream with npx skills add PP-Namias/Portfolio --skill opennext-cloudflare. Copyright stays with the author.

OpenNext Cloudflare Skill

Deploy Next.js applications to Cloudflare Workers using the @opennextjs/cloudflare adapter.

When to use this skill

• Deploying to Cloudflare Workers
• Troubleshooting Cloudflare deployment issues
• Configuring Cloudflare-specific features (KV, R2, D1)
• Setting up CI/CD for Cloudflare

Current setup

• Adapter: @opennextjs/cloudflare v1.19.11
• Next.js: v16.2.9 (--dangerouslyUseUnsupportedNextVersion)
• Worker name: namias
• Compatibility flags: nodejs_compat

Files

Build and deploy

Local build

npx @opennextjs/cloudflare build

Deploy to Cloudflare

npx wrangler deploy

CI/CD

Deployment happens via GitHub Actions on push to main:

• .github/workflows/cloudflare-deploy.yml
• Uses CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID

Common issues

"Cloudflare worker does not have a proxy.ts"

• Cause: src/proxy.ts is not supported in newer OpenNext versions
• Fix: Rename to src/middleware.ts

"Unsupported version of Next.js detected"

• Cause: OpenNext doesn't officially support Next.js 16 yet
• Fix: Add --dangerouslyUseUnsupportedNextVersion flag to build command

"Node.js compatibility mode is required"

• Cause: Missing nodejs_compat compatibility flag
• Fix: Add "compatibility_flags": ["nodejs_compat"] to wrangler.jsonc

"Global fetch is not available"

• Cause: Missing global_fetch_strictly_public flag
• Fix: Add "compatibility_flags": ["global_fetch_strictly_public"] to wrangler.jsonc

Environment variables

Set in Cloudflare dashboard or wrangler.jsonc:

Checklist

• wrangler.jsonc has correct compatibility flags
• src/middleware.ts exists (not proxy.ts)
• Environment variables set in Cloudflare dashboard
• CI/CD workflow has correct secrets
• Build succeeds with npx @opennextjs/cloudflare build