Wrangler Config Generator

wrangler.toml is the configuration file for Cloudflare Workers and Pages projects. It tells Wrangler (Cloudflare's CLI) how to build, deploy, and configure your worker — including its name, entry point, bindings (KV, D1, R2, Durable Objects), environment variables, and routing rules.

Cloudflare Workers are serverless scripts that run at the edge. Cloudflare Pages is a full-stack platform for deploying frontend apps with optional Functions (which are also Workers under the hood). For Pages, you set pages_build_output_dir instead of main. For Workers, you point main to your TypeScript/JavaScript entry file.

The compatibility_date field controls which version of Cloudflare's runtime APIs your Worker uses. Cloudflare introduces breaking changes on new dates — setting this date pins your Worker to a specific runtime behavior. Always use a recent date for new projects. Changing it later may require code updates, so test after bumping.

Enable node_compat when your Worker imports Node.js built-in modules like path, crypto, buffer, or stream. Cloudflare polyfills many Node.js APIs in its runtime. Without this flag, imports like import { createHash } from 'crypto' will fail. Note: not all Node.js APIs are supported — check Cloudflare's compatibility matrix.

Run `wrangler kv:namespace create MY_NAMESPACE` to create a KV namespace and get its ID. For D1, run `wrangler d1 create my-database`. Both commands output the IDs you need. For production, you need a separate namespace ID; for local dev, Wrangler uses a local SQLite/in-memory store unless you provide a preview_id.