wrangler

Run wrangler deploy from your project directory after configuring wrangler.jsonc with your Worker name, main entry point, and compatibility date. Use wrangler deploy --dry-run to validate first, or wrangler deploy --env staging for a specific environment.

Add a d1_databases array with binding name, database_name, and database_id to wrangler.jsonc. Create the database with wrangler d1 create, then run wrangler types to generate TypeScript bindings for the DB object.

Use wrangler.jsonc because newer Wrangler features are JSON-only and it supports comments. The TOML format still works but may not support the latest configuration options.

By default wrangler dev uses local storage simulation for bindings. Set remote: true on specific bindings in your config to connect to real resources like R2 buckets or Vectorize indexes while running locally.

Bindings are undefined when the binding name in your code does not exactly match the name in wrangler.jsonc, or when types are stale. Verify the config with wrangler check and regenerate types with wrangler types.

Use wrangler secret put NAME to set secrets interactively or pipe values via stdin for production. For local development, place secrets in a .dev.vars file, which is never committed to version control.