☁︎
Integration
DeployDoc for Cloudflare Pages & Workers
Find the Node-incompatibility, nodejs_compat and bundling problems that make Workers fail in production but pass in wrangler dev.
Outbound integrationEducational recipe — paste wrangler.toml and a build log for a runtime audit.
What commonly breaks on Cloudflare Pages & Workers
- Missing nodejs_compat compatibility flag.
- Importing sharp, puppeteer, canvas, or other native-binding packages.
- child_process / dgram / fs.watch references reachable from production code.
- __dirname / __filename usage under ESM bundling.
- compatibility_date too old to enable modern Node shims.
What DeployDoc checks
- wrangler.toml + Pages compatibility flags.
- Dependency tree for known Worker-incompatible packages.
- Static import scan for Node-only modules.
- compatibility_date freshness.
Can automate
- • wrangler.toml audit.
- • Dependency compatibility flagging.
- • Build-log triage.
Cannot automate
- • Swapping a Node-only library for a Worker-compatible one.
- • Editing wrangler.toml in your repo.
- • Triggering Cloudflare deploys.
Get started with Cloudflare Pages & Workers
Run a diagnosis on a recent failed build, or connect Cloudflare Pages & Workers for one-click fixes where supported.