# What Is the wrangler.toml Configuration File in Impeccable? > Discover the wrangler.toml file in Impeccable. Learn how it guides Cloudflare Pages for building, previewing, and deploying your site. Understand project name, compatibility, and asset locations. - Repository: [Paul Bakaus/impeccable](https://github.com/pbakaus/impeccable) - Tags: api-reference - Published: 2026-03-09 --- **The [`wrangler.toml`](https://github.com/pbakaus/impeccable/blob/main/wrangler.toml) configuration file tells Cloudflare Pages how to build, preview, and deploy the Impeccable site by defining the project name, runtime compatibility date, and the location of static build assets.** The [`wrangler.toml`](https://github.com/pbakaus/impeccable/blob/main/wrangler.toml) configuration file sits at the root of the **pbakaus/impeccable** repository and serves as the control center for Cloudflare Pages deployment. This single configuration bridges the local build pipeline with Cloudflare's global edge network, ensuring the static site generated by [`scripts/build.js`](https://github.com/pbakaus/impeccable/blob/main/scripts/build.js) reaches production correctly. ## Core Settings in Impeccable's wrangler.toml The file contains three critical directives that govern how Cloudflare handles the project: - **`name = "impeccable-style"`** — Identifies the project within your Cloudflare account. - **`compatibility_date = "2024-12-01"`** — Locks the Cloudflare Workers runtime to a specific version, ensuring consistent behavior across builds. - **`pages_build_output_dir = "./build"`** — Points to the directory where [`scripts/build.js`](https://github.com/pbakaus/impeccable/blob/main/scripts/build.js) writes static files; Cloudflare Pages serves the contents of this folder as the live site. These settings reside in [`wrangler.toml`](https://github.com/pbakaus/impeccable/blob/main/wrangler.toml) at lines 1–3, establishing the foundation for the deployment pipeline. ## How wrangler.toml Integrates with NPM Scripts The configuration file works in tandem with the npm scripts defined in **[`package.json`](https://github.com/pbakaus/impeccable/blob/main/package.json)** (lines 25–26). The scripts orchestrate the build process and Wrangler CLI commands: ```json "preview": "bun run build && wrangler pages dev", "deploy": "bun run build && wrangler pages deploy build/" ``` **`preview`** compiles the site and launches `wrangler pages dev`, which reads [`wrangler.toml`](https://github.com/pbakaus/impeccable/blob/main/wrangler.toml) to determine the project context and serves the `./build` directory locally. **`deploy`** executes the same build step, then pushes the `./build` folder to Cloudflare Pages using the configuration defined in [`wrangler.toml`](https://github.com/pbakaus/impeccable/blob/main/wrangler.toml). ## The Complete Deployment Workflow Together, these components create an automated workflow for the Impeccable project: 1. **Build** — `bun run build` executes [`scripts/build.js`](https://github.com/pbakaus/impeccable/blob/main/scripts/build.js) to generate static assets in the `./build` directory. 2. **Preview** — `wrangler pages dev` references [`wrangler.toml`](https://github.com/pbakaus/impeccable/blob/main/wrangler.toml) to start a local server mimicking the Cloudflare production environment. 3. **Deploy** — `wrangler pages deploy build/` uploads the contents of `./build` to the live Cloudflare Pages domain associated with the `impeccable-style` project name. Without [`wrangler.toml`](https://github.com/pbakaus/impeccable/blob/main/wrangler.toml), the Wrangler CLI would not know which Cloudflare project to target, which runtime compatibility to enforce, or which directory contains the deployable assets. ## Practical Commands for Development ### Run a Local Preview Server Build the site and start the Cloudflare Pages development server: ```bash npm run preview # Executes: bun run build && wrangler pages dev ``` ### Deploy to Production Build and push the static assets to Cloudflare Pages: ```bash npm run deploy # Executes: bun run build && wrangler pages deploy build/ ``` ### Manual Wrangler Invocation Serve an already-built folder without triggering the build script: ```bash wrangler pages dev ./build ``` ## Summary - The **[`wrangler.toml`](https://github.com/pbakaus/impeccable/blob/main/wrangler.toml) configuration file** in Impeccable defines the Cloudflare Pages project name (`impeccable-style`), runtime compatibility date (`2024-12-01`), and build output directory (`./build`). - **[`package.json`](https://github.com/pbakaus/impeccable/blob/main/package.json)** scripts automate the workflow by combining the build step with Wrangler CLI commands that read this configuration. - **[`scripts/build.js`](https://github.com/pbakaus/impeccable/blob/main/scripts/build.js)** generates the static content that `pages_build_output_dir` points to, completing the deployment chain. - Removing or misconfiguring [`wrangler.toml`](https://github.com/pbakaus/impeccable/blob/main/wrangler.toml) would break both local preview and production deployment capabilities. ## Frequently Asked Questions ### What happens if I change the pages_build_output_dir in wrangler.toml? Changing `pages_build_output_dir` redirects Cloudflare Pages to look for deployable assets in a different folder. If you modify this value without updating [`scripts/build.js`](https://github.com/pbakaus/impeccable/blob/main/scripts/build.js) to write to the new location, the deployment will fail because Wrangler will find an empty or non-existent directory. Always ensure this path matches the actual output directory of your build process. ### Why does Impeccable use a compatibility_date in wrangler.toml? The `compatibility_date = "2024-12-01"` setting pins the Cloudflare Workers runtime to a specific version released on that date. This prevents unexpected behavior changes when Cloudflare updates its global infrastructure, ensuring that the Impeccable site runs on a stable, predictable runtime environment regardless of when you deploy. ### Can I deploy Impeccable to Cloudflare Pages without using wrangler.toml? Technically, you could use the Wrangler CLI with command-line flags to specify the project name and build directory, but this would sacrifice repeatability and introduce human error. The [`wrangler.toml`](https://github.com/pbakaus/impeccable/blob/main/wrangler.toml) file eliminates the need to remember these parameters for every command, standardizing the deployment process across different environments and team members.