From f2a0f1b933f04823654b95eb8176af6ca6b0e82d Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Mon, 9 Feb 2026 11:01:41 +0000 Subject: [PATCH] docs: document WRANGLER_COMMAND environment variable for custom builds Co-Authored-By: pbacondarwin@cloudflare.com --- .../docs/workers/wrangler/custom-builds.mdx | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/src/content/docs/workers/wrangler/custom-builds.mdx b/src/content/docs/workers/wrangler/custom-builds.mdx index 2345225d9a5d1ee..c5a0fb29f89947c 100644 --- a/src/content/docs/workers/wrangler/custom-builds.mdx +++ b/src/content/docs/workers/wrangler/custom-builds.mdx @@ -45,3 +45,29 @@ Example: ``` + +## `WRANGLER_COMMAND` environment variable + +When Wrangler runs your custom build command, it sets the `WRANGLER_COMMAND` environment variable so your build script can detect which Wrangler command triggered the build. This allows you to customize the build process based on the deployment context. + +The possible values are: + +| Value | Wrangler command triggered | +| ------------------ | ---------------------------------------- | +| `dev` | `wrangler dev` | +| `deploy` | `wrangler deploy` | +| `versions upload` | `wrangler versions upload` | +| `types` | `wrangler types` | + +For example, you can use this to apply different build settings for development and production: + +```bash +#!/bin/bash +if [ "$WRANGLER_COMMAND" = "dev" ]; then + echo "Building for development..." + # run a development build +else + echo "Building for production..." + # run a production build +fi +```