WranglerCommand
WranglerCommand
is used 0
times on 0
pages.
Pages which use WranglerCommand
Used 0 times.
Pages
Partials
The WranglerCommand
component documents the available options for a given command.
This is generated using the Wrangler version in the cloudflare-docs
repository ↗.
import { WranglerCommand } from "~/components";
npx wrangler deploy [SCRIPT]
pnpm wrangler deploy [SCRIPT]
yarn wrangler deploy [SCRIPT]
-
[SCRIPT]
stringThe path to an entry point for your Worker
-
--name
stringName of the Worker
-
--no-bundle
boolean default: falseSkip internal build steps and directly deploy Worker
-
--outdir
stringOutput directory for the bundled Worker
-
--outfile
stringOutput file for the bundled worker
-
--compatibility-date
stringDate to use for compatibility checks
-
--compatibility-flags
string alias: --compatibility-flagFlags to use for compatibility checks
-
--latest
boolean default: falseUse the latest version of the Workers runtime
-
--assets
stringStatic assets to be served. Replaces Workers Sites.
-
--var
stringA key-value pair to be injected into the script as a variable
-
--define
stringA key-value pair to be substituted in the script
-
--alias
stringA module pair to be substituted in the script
-
--triggers
string aliases: --schedule, --schedulescron schedules to attach
-
--routes
string alias: --routeRoutes to upload
-
--domains
string alias: --domainCustom domains to deploy to
-
--jsx-factory
stringThe function that is called for each JSX element
-
--jsx-fragment
stringThe function that is called for each JSX fragment
-
--tsconfig
stringPath to a custom tsconfig.json file
-
--minify
booleanMinify the Worker
-
--dry-run
booleanDon't actually deploy
-
--metafile
stringPath to output build metadata from esbuild. If flag is used without a path, defaults to 'bundle-meta.json' inside the directory specified by --outdir.
-
--keep-vars
boolean default: falseWhen not used (or set to false), Wrangler will delete all vars before setting those found in the Wrangler configuration. When used (and set to true), the environment variables are not deleted before the deployment. If you set variables via the dashboard you probably want to use this flag. Note that secrets are never deleted by deployments.
-
--logpush
booleanSend Trace Events from this Worker to Workers Logpush. This will not configure a corresponding Logpush job automatically.
-
--upload-source-maps
booleanInclude source maps when uploading this Worker.
-
--old-asset-ttl
numberExpire old assets in given seconds rather than immediate deletion.
-
--dispatch-namespace
stringName of a dispatch namespace to deploy the Worker to (Workers for Platforms)
npx wrangler d1 execute [DATABASE]
pnpm wrangler d1 execute [DATABASE]
yarn wrangler d1 execute [DATABASE]
-
[DATABASE]
string requiredThe name or binding of the DB
-
--yes
boolean alias: --yAnswer "yes" to any prompts
-
--local
booleanExecute commands/files against a local DB for use with wrangler dev
-
--remote
booleanExecute commands/files against a remote DB for use with wrangler dev
-
--file
stringA .sql file to ingest
-
--command
stringA single SQL statement to execute
-
--persist-to
stringSpecify directory to use for local persistence (for --local)
-
--json
boolean default: falseReturn output as clean JSON
-
--preview
boolean default: falseExecute commands/files against a preview D1 DB
import { WranglerCommand } from "~/components";
<WranglerCommand command="deploy" />
<WranglerCommand command="d1 execute" />
Was this helpful?
- Resources
- API
- New to Cloudflare?
- Directory
- Sponsorships
- Open Source
- Support
- Help Center
- System Status
- Compliance
- GDPR
- Company
- cloudflare.com
- Our team
- Careers
- © 2025 Cloudflare, Inc.
- Privacy Policy
- Terms of Use
- Report Security Issues
- Trademark