Skip to content

docs: document WRANGLER_COMMAND environment variable for custom builds #28207

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MattieTK merged 1 commit into from
Apr 20, 2026
Merged

docs: document WRANGLER_COMMAND environment variable for custom builds #28207

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions src/content/docs/workers/wrangler/custom-builds.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,3 +45,29 @@ Example:
```

</WranglerConfig>

## `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
```
Loading