Wrangler CLI
Wrangler is a command-line tool for building with Cloudflare developer products
| Type | RawConfig |
|---|---|
| File match |
wrangler.json
wrangler.jsonc
wrangler.toml
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/wrangler-cli/latest.json |
| Source | https://www.unpkg.com/wrangler/config-schema.json |
Validate with Lintel
npx @lintel/lintel check
Definitions
The env section defines overrides for the configuration for different environments.
All environment fields can be specified at the top level of the config indicating the default environment settings.
- Some fields are inherited and overridable in each environment.
- But some are not inherited and must be explicitly specified in every environment, if they are specified at the top level.
For more information, see the documentation at https://developers.cloudflare.com/workers/cli-wrangler/configuration#environments
{}
The name of your Worker. Alphanumeric + dashes only.
This is the ID of the account associated with your zone. You might have more than one account, so make sure to use the ID of the account associated with the zone/route you provide, if you provide one. It can also be specified through the CLOUDFLARE_ACCOUNT_ID environment variable.
A date in the form yyyy-mm-dd, which will be used to determine which version of the Workers runtime is used.
More details at https://developers.cloudflare.com/workers/configuration/compatibility-dates
A list of flags that enable features from upcoming features of the Workers runtime, usually used together with compatibility_date.
More details at https://developers.cloudflare.com/workers/configuration/compatibility-flags/
[]
The entrypoint/path to the JavaScript file that will be executed.
If true then Wrangler will traverse the file tree below base_dir; Any files that match rules will be included in the deployed Worker. Defaults to true if no_bundle is true, otherwise false.
Determines whether Wrangler will preserve bundled file names. Defaults to false. If left unset, files will be named using the pattern ${fileHash}-${basename}, for example, 34de60b44167af5c5a709e62a4e20c4f18c9e3b6-favicon.ico.
The directory in which module rules should be evaluated when including additional files into a Worker deployment. This defaults to the directory containing the main entry point of the Worker if not specified.
Whether we use
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#workersdev
Whether we use
A list of routes that your Worker should be published to. Only one of routes or route is required.
Only required when workers_dev is false, and there's no scheduled Worker (see triggers)
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#types-of-routes
Path to a custom tsconfig
The function to use to replace jsx syntax.
The function to use to replace jsx fragment syntax.
A list of migrations that should be uploaded with your Worker.
These define changes in your Durable Object declarations.
More details at https://developers.cloudflare.com/workers/learning/using-durable-objects#configuring-durable-object-classes-with-migrations
[]
"Cron" definitions to trigger a Worker's "scheduled" function.
Lets you call Workers periodically, much like a cron job.
More details here https://developers.cloudflare.com/workers/platform/cron-triggers
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#triggers
{
"crons": []
}
1 nested properties
2 nested properties
Maximum allowed CPU time for a Worker's invocation in milliseconds
Maximum allowed number of fetch requests that a Worker's invocation can execute
An ordered list of rules that define which modules to import, and what type to import them as. You will need to specify rules to use Text, Data, and CompiledWasm modules, or when you wish to have a .js file be treated as an ESModule instead of CommonJS.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#bundling
Configures a custom build step to be run by Wrangler when building your Worker.
Refer to the custom builds documentation for more details.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#custom-builds
{
"watch_dir": "./src"
}
3 nested properties
The command used to build your Worker. On Linux and macOS, the command is executed in the sh shell and the cmd shell for Windows. The && and || shell operators may be used.
The directory in which the command is executed.
The directory to watch for changes while using wrangler dev, defaults to the current working directory
Skip internal build steps and directly deploy script
Minify the script before uploading.
Set the name property to the original name for functions and classes renamed during minification.
Designates this Worker as an internal-only "first-party" Worker.
List of bindings that you will send to logfwdr
{
"bindings": []
}
1 nested properties
Send Trace Events from this Worker to Workers Logpush.
This will not configure a corresponding Logpush job automatically.
For more information about Workers Logpush, see: https://blog.cloudflare.com/logpush-for-workers/
Include source maps when uploading this worker.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#source-maps
Specify how the Worker should be located to minimize round-trip time.
More details: https://developers.cloudflare.com/workers/platform/smart-placement/
5 nested properties
Absolute path to assets directory
Name of env binding property in the User Worker.
How to handle HTML requests.
How to handle requests that do not match an asset.
Matches will be routed to the User Worker, and matches to negative rules will go to the Asset Worker.
Can also be true, indicating that every request should be routed to the User Worker.
4 nested properties
If observability is enabled for this Worker
The sampling rate
5 nested properties
The sampling rate
Set to false to disable invocation logs
If logs should be persisted to the Cloudflare observability platform where they can be queried in the dashboard.
What destinations logs emitted from the Worker should be sent to.
[]
4 nested properties
The sampling rate
If traces should be persisted to the Cloudflare observability platform where they can be queried in the dashboard.
What destinations traces emitted from the Worker should be sent to.
[]
Specify the compliance region mode of the Worker.
Although if the user does not specify a compliance region, the default is public, it can be set to undefined in configuration to delegate to the CLOUDFLARE_COMPLIANCE_REGION environment variable.
Configuration for Python modules.
1 nested properties
A list of glob patterns to exclude files from the python_modules directory when bundling.
Patterns are relative to the python_modules directory and use glob syntax.
[
"***.pyc"
]
A map of values to substitute when deploying your Worker.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
{}
A map of environment variables to set when deploying your Worker.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
{}
Secrets configuration (experimental).
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
1 nested properties
List of secret names that are required by your Worker. When defined, this property:
- Replaces .dev.vars/.env/process.env inference for type generation
- Enables local dev validation with warnings for missing secrets
A list of durable objects that your Worker should be bound to.
For more information about Durable Objects, see the documentation at https://developers.cloudflare.com/workers/learning/using-durable-objects
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#durable-objects
{
"bindings": []
}
1 nested properties
A list of workflows that your Worker should be bound to.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Configuration in wrangler for Cloudchamber
6 nested properties
Container related configuration
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
These specify any Workers KV Namespaces you want to access from inside your Worker.
To learn more about KV Namespaces, see the documentation at https://developers.cloudflare.com/workers/learning/how-kv-works
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#kv-namespaces
[]
These specify bindings to send email from inside your Worker.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#email-bindings
[]
Specifies Queues that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#queues
{
"consumers": [],
"producers": []
}
2 nested properties
Producer bindings
Consumer configuration
Specifies R2 buckets that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#r2-buckets
[]
Specifies D1 databases that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#d1-databases
[]
Specifies Vectorize indexes that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#vectorize-indexes
[]
Specifies AI Search namespace bindings that are bound to this Worker environment. Each binding is scoped to a namespace and allows dynamic instance CRUD within it.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies AI Search instance bindings that are bound to this Worker environment. Each binding is bound directly to a single pre-existing instance within the "default" namespace.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies Hyperdrive configs that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#hyperdrive
[]
Specifies service bindings (Worker-to-Worker) that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#service-bindings
[]
Specifies analytics engine datasets that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#analytics-engine-datasets
[]
A browser that will be usable from the Worker.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#browser-rendering
{}
2 nested properties
Whether the Browser binding should be remote or not in local development
Binding to the AI project.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#workers-ai
{}
3 nested properties
Whether the AI binding should be remote or not in local development
Binding to Cloudflare Images
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#images
{}
2 nested properties
Whether the Images binding should be remote or not in local development
Binding to Cloudflare Media Transformations
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
{}
2 nested properties
Whether the Media binding should be remote or not
Binding to Cloudflare Stream
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
{}
2 nested properties
Whether the Stream binding should be remote or not in local development
Binding to the Worker Version's metadata
1 nested properties
"Unsafe" tables for features that aren't directly supported by wrangler.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
{}
3 nested properties
A set of bindings that should be put into a Worker's upload metadata without changes. These can be used to implement bindings for features that haven't released and aren't supported directly by wrangler or miniflare.
Arbitrary key/value pairs that will be included in the uploaded metadata. Values specified here will always be applied to metadata last, so can add new or override existing fields.
Used for internal capnp uploads for the Workers runtime
Specifies a list of mTLS certificates that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#mtls-certificates
[]
Specifies a list of Tail Workers that are bound to this Worker environment
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies a list of Streaming Tail Workers that are bound to this Worker environment
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies namespace bindings that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#dispatch-namespace-bindings-workers-for-platforms
[]
Specifies list of Pipelines bound to this Worker environment
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies Secret Store bindings that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
DO NOT USE. Hello World Binding Config to serve as an explanatory example.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies rate limit bindings that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies Worker Loader bindings that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies VPC services that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies VPC networks that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
The directory of static assets to serve.
The presence of this field in a Wrangler configuration file indicates a Pages project, and will prompt the handling of the configuration file according to the Pages-specific validation rules.
A boolean to enable "legacy" style wrangler environments (from Wrangler v1). These have been superseded by Services, but there may be projects that won't (or can't) use them. If you're using a legacy environment, you can set this to true to enable it.
Whether Wrangler should send usage metrics to Cloudflare for this project.
When defined this will override any user settings. Otherwise, Wrangler will use the user's preference.
10 nested properties
IP address for the local dev server to listen on,
Port for the local dev server to listen on
Port for the local dev server's inspector to listen on
IP address for the local dev server's inspector to listen on
Protocol that local wrangler dev server listens to requests on.
Protocol that wrangler dev forwards requests on
Setting this to http is not currently implemented for remote mode. See https://github.com/cloudflare/workers-sdk/issues/583
Host to forward requests to, defaults to the host of the first route of project
When developing, whether to build and connect to containers. This requires a Docker daemon to be running. Defaults to true.
Re-generate your worker types when your Wrangler configuration file changes.
The definition of a Worker Site, a feature that lets you upload static assets with your Worker.
More details at https://developers.cloudflare.com/workers/platform/sites
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#workers-sites
4 nested properties
The directory containing your static assets.
It must be a path relative to your Wrangler configuration file. Example: bucket = "./public"
If there is a site field then it must contain this bucket field.
The location of your Worker script.
An exclusive list of .gitignore-style patterns that match file or directory names from your bucket location. Only matched items will be uploaded. Example: include = ["upload_dir"]
[]
A list of .gitignore-style patterns that match files or directories in your bucket that should be excluded from uploads. Example: exclude = ["ignore_dir"]
[]
A list of wasm modules that your worker should be bound to. This is the "legacy" way of binding to a wasm module. ES module workers should do proper module imports.
A list of text files that your worker should be bound to. This is the "legacy" way of binding to a text file. ES module workers should do proper module imports.
A list of data files that your worker should be bound to. This is the "legacy" way of binding to a data file. ES module workers should do proper module imports.
A map of module aliases. Lets you swap out a module for any others. Corresponds with esbuild's alias config
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#module-aliasing
By default, the Wrangler configuration file is the source of truth for your environment configuration, like a terraform file.
If you change your vars in the dashboard, wrangler will override/delete them on its next deploy.
If you want to keep your dashboard vars when wrangler deploys, set this field to true.
The raw environment configuration that we read from the config file.
All the properties are optional, and will be replaced with defaults in the configuration that is used in the rest of the codebase.
The name of your Worker. Alphanumeric + dashes only.
This is the ID of the account associated with your zone. You might have more than one account, so make sure to use the ID of the account associated with the zone/route you provide, if you provide one. It can also be specified through the CLOUDFLARE_ACCOUNT_ID environment variable.
A date in the form yyyy-mm-dd, which will be used to determine which version of the Workers runtime is used.
More details at https://developers.cloudflare.com/workers/configuration/compatibility-dates
A list of flags that enable features from upcoming features of the Workers runtime, usually used together with compatibility_date.
More details at https://developers.cloudflare.com/workers/configuration/compatibility-flags/
[]
The entrypoint/path to the JavaScript file that will be executed.
If true then Wrangler will traverse the file tree below base_dir; Any files that match rules will be included in the deployed Worker. Defaults to true if no_bundle is true, otherwise false.
Determines whether Wrangler will preserve bundled file names. Defaults to false. If left unset, files will be named using the pattern ${fileHash}-${basename}, for example, 34de60b44167af5c5a709e62a4e20c4f18c9e3b6-favicon.ico.
The directory in which module rules should be evaluated when including additional files into a Worker deployment. This defaults to the directory containing the main entry point of the Worker if not specified.
Whether we use
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#workersdev
Whether we use
A list of routes that your Worker should be published to. Only one of routes or route is required.
Only required when workers_dev is false, and there's no scheduled Worker (see triggers)
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#types-of-routes
Path to a custom tsconfig
The function to use to replace jsx syntax.
The function to use to replace jsx fragment syntax.
A list of migrations that should be uploaded with your Worker.
These define changes in your Durable Object declarations.
More details at https://developers.cloudflare.com/workers/learning/using-durable-objects#configuring-durable-object-classes-with-migrations
[]
"Cron" definitions to trigger a Worker's "scheduled" function.
Lets you call Workers periodically, much like a cron job.
More details here https://developers.cloudflare.com/workers/platform/cron-triggers
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#triggers
{
"crons": []
}
1 nested properties
2 nested properties
Maximum allowed CPU time for a Worker's invocation in milliseconds
Maximum allowed number of fetch requests that a Worker's invocation can execute
An ordered list of rules that define which modules to import, and what type to import them as. You will need to specify rules to use Text, Data, and CompiledWasm modules, or when you wish to have a .js file be treated as an ESModule instead of CommonJS.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#bundling
Configures a custom build step to be run by Wrangler when building your Worker.
Refer to the custom builds documentation for more details.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#custom-builds
{
"watch_dir": "./src"
}
3 nested properties
The command used to build your Worker. On Linux and macOS, the command is executed in the sh shell and the cmd shell for Windows. The && and || shell operators may be used.
The directory in which the command is executed.
The directory to watch for changes while using wrangler dev, defaults to the current working directory
Skip internal build steps and directly deploy script
Minify the script before uploading.
Set the name property to the original name for functions and classes renamed during minification.
Designates this Worker as an internal-only "first-party" Worker.
List of bindings that you will send to logfwdr
{
"bindings": []
}
1 nested properties
Send Trace Events from this Worker to Workers Logpush.
This will not configure a corresponding Logpush job automatically.
For more information about Workers Logpush, see: https://blog.cloudflare.com/logpush-for-workers/
Include source maps when uploading this worker.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#source-maps
Specify how the Worker should be located to minimize round-trip time.
More details: https://developers.cloudflare.com/workers/platform/smart-placement/
5 nested properties
Absolute path to assets directory
Name of env binding property in the User Worker.
How to handle HTML requests.
How to handle requests that do not match an asset.
Matches will be routed to the User Worker, and matches to negative rules will go to the Asset Worker.
Can also be true, indicating that every request should be routed to the User Worker.
4 nested properties
If observability is enabled for this Worker
The sampling rate
5 nested properties
The sampling rate
Set to false to disable invocation logs
If logs should be persisted to the Cloudflare observability platform where they can be queried in the dashboard.
What destinations logs emitted from the Worker should be sent to.
[]
4 nested properties
The sampling rate
If traces should be persisted to the Cloudflare observability platform where they can be queried in the dashboard.
What destinations traces emitted from the Worker should be sent to.
[]
Specify the compliance region mode of the Worker.
Although if the user does not specify a compliance region, the default is public, it can be set to undefined in configuration to delegate to the CLOUDFLARE_COMPLIANCE_REGION environment variable.
Configuration for Python modules.
1 nested properties
A list of glob patterns to exclude files from the python_modules directory when bundling.
Patterns are relative to the python_modules directory and use glob syntax.
[
"***.pyc"
]
A map of values to substitute when deploying your Worker.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
{}
A map of environment variables to set when deploying your Worker.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
{}
Secrets configuration (experimental).
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
1 nested properties
List of secret names that are required by your Worker. When defined, this property:
- Replaces .dev.vars/.env/process.env inference for type generation
- Enables local dev validation with warnings for missing secrets
A list of durable objects that your Worker should be bound to.
For more information about Durable Objects, see the documentation at https://developers.cloudflare.com/workers/learning/using-durable-objects
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#durable-objects
{
"bindings": []
}
1 nested properties
A list of workflows that your Worker should be bound to.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Configuration in wrangler for Cloudchamber
6 nested properties
Container related configuration
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
These specify any Workers KV Namespaces you want to access from inside your Worker.
To learn more about KV Namespaces, see the documentation at https://developers.cloudflare.com/workers/learning/how-kv-works
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#kv-namespaces
[]
These specify bindings to send email from inside your Worker.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#email-bindings
[]
Specifies Queues that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#queues
{
"consumers": [],
"producers": []
}
2 nested properties
Producer bindings
Consumer configuration
Specifies R2 buckets that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#r2-buckets
[]
Specifies D1 databases that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#d1-databases
[]
Specifies Vectorize indexes that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#vectorize-indexes
[]
Specifies AI Search namespace bindings that are bound to this Worker environment. Each binding is scoped to a namespace and allows dynamic instance CRUD within it.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies AI Search instance bindings that are bound to this Worker environment. Each binding is bound directly to a single pre-existing instance within the "default" namespace.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies Hyperdrive configs that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#hyperdrive
[]
Specifies service bindings (Worker-to-Worker) that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#service-bindings
[]
Specifies analytics engine datasets that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#analytics-engine-datasets
[]
A browser that will be usable from the Worker.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#browser-rendering
{}
2 nested properties
Whether the Browser binding should be remote or not in local development
Binding to the AI project.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#workers-ai
{}
3 nested properties
Whether the AI binding should be remote or not in local development
Binding to Cloudflare Images
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#images
{}
2 nested properties
Whether the Images binding should be remote or not in local development
Binding to Cloudflare Media Transformations
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
{}
2 nested properties
Whether the Media binding should be remote or not
Binding to Cloudflare Stream
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
{}
2 nested properties
Whether the Stream binding should be remote or not in local development
Binding to the Worker Version's metadata
1 nested properties
"Unsafe" tables for features that aren't directly supported by wrangler.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
{}
3 nested properties
A set of bindings that should be put into a Worker's upload metadata without changes. These can be used to implement bindings for features that haven't released and aren't supported directly by wrangler or miniflare.
Arbitrary key/value pairs that will be included in the uploaded metadata. Values specified here will always be applied to metadata last, so can add new or override existing fields.
Used for internal capnp uploads for the Workers runtime
Specifies a list of mTLS certificates that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#mtls-certificates
[]
Specifies a list of Tail Workers that are bound to this Worker environment
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies a list of Streaming Tail Workers that are bound to this Worker environment
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies namespace bindings that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
For reference, see https://developers.cloudflare.com/workers/wrangler/configuration/#dispatch-namespace-bindings-workers-for-platforms
[]
Specifies list of Pipelines bound to this Worker environment
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies Secret Store bindings that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
DO NOT USE. Hello World Binding Config to serve as an explanatory example.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies rate limit bindings that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies Worker Loader bindings that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies VPC services that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Specifies VPC networks that are bound to this Worker environment.
NOTE: This field is not automatically inherited from the top level environment, and so must be specified in every named environment.
[]
Configuration in wrangler for Durable Object Migrations
A unique identifier for this migration.
The new Durable Objects being defined.
The new SQLite Durable Objects being defined.
The Durable Objects being renamed.
The Durable Objects being removed.
Maximum allowed CPU time for a Worker's invocation in milliseconds
Maximum allowed number of fetch requests that a Worker's invocation can execute
A bundling resolver rule, defining the modules type for paths that match the specified globs.
The possible types for a Rule.
Absolute path to assets directory
Name of env binding property in the User Worker.
How to handle HTML requests.
How to handle requests that do not match an asset.
Matches will be routed to the User Worker, and matches to negative rules will go to the Asset Worker.
Can also be true, indicating that every request should be routed to the User Worker.
If observability is enabled for this Worker
The sampling rate
5 nested properties
The sampling rate
Set to false to disable invocation logs
If logs should be persisted to the Cloudflare observability platform where they can be queried in the dashboard.
What destinations logs emitted from the Worker should be sent to.
[]
4 nested properties
The sampling rate
If traces should be persisted to the Cloudflare observability platform where they can be queried in the dashboard.
What destinations traces emitted from the Worker should be sent to.
[]
The name of the binding used to refer to the Workflow
The name of the Workflow
The exported class name of the Workflow
The script where the Workflow is defined (if it's external to this Worker)
Whether the Workflow should be remote or not in local development
Optional limits for the Workflow
1 nested properties
Maximum number of steps a Workflow instance can execute
Configuration in wrangler for Cloudchamber
Configuration for a container application
The path to a Dockerfile, or an image URI for the Cloudflare registry.
The class name of the Durable Object the container is connected to.
Name of the application
Number of maximum application instances.
Build context of the application.
Image variables available to the image at build-time only. For runtime env vars, refer to https://developers.cloudflare.com/containers/examples/env-vars-and-secrets/
The scheduling policy of the application
The instance type to be used for the container. Select from one of the following named instance types: - lite: 1/16 vCPU, 256 MiB memory, and 2 GB disk - basic: 1/4 vCPU, 1 GiB memory, and 4 GB disk - standard-1: 1/2 vCPU, 4 GiB memory, and 8 GB disk - standard-2: 1 vCPU, 6 GiB memory, and 12 GB disk - standard-3: 2 vCPU, 8 GiB memory, and 16 GB disk - standard-4: 4 vCPU, 12 GiB memory, and 20 GB disk - dev: 1/16 vCPU, 256 MiB memory, and 2 GB disk (deprecated, use "lite" instead) - standard: 1 vCPU, 4 GiB memory, and 4 GB disk (deprecated, use "standard-1" instead)
Customers on an enterprise plan have the additional option to set custom limits.
2 nested properties
If enabled, those with write access to a container will be able to SSH into it through Wrangler.
Port that the SSH service is running on
SSH public keys to put in the container's authorized_keys file.
Trusted user CA keys to put in the container's trusted_user_ca_keys file.
Configures what percentage of instances should be updated at each step of a rollout. You can specify this as a single number, or an array of numbers.
If this is a single number, each step will progress by that percentage. The options are 5, 10, 20, 25, 50 or 100.
If this is an array, each step specifies the cumulative rollout progress. The final step must be 100.
This can be overridden adhoc by deploying with the --containers-rollout=immediate flag, which will roll out to 100% of instances in one step.
[
10,
100
]
Configures the grace period (in seconds) for active instances before being shutdown during a rollout.
The name of the service tail events will be forwarded to.
(Optional) The environment of the service.
The name of the service streaming tail events will be forwarded to.
Name of the service handling the outbound requests
(Optional) Name of the environment handling the outbound requests.
(Optional) List of parameter names, for sending context from your dispatch Worker to the outbound handler
IP address for the local dev server to listen on,
Port for the local dev server to listen on
Port for the local dev server's inspector to listen on
IP address for the local dev server's inspector to listen on
Protocol that local wrangler dev server listens to requests on.
Protocol that wrangler dev forwards requests on
Setting this to http is not currently implemented for remote mode. See https://github.com/cloudflare/workers-sdk/issues/583
Host to forward requests to, defaults to the host of the first route of project
When developing, whether to build and connect to containers. This requires a Docker daemon to be running. Defaults to true.
Re-generate your worker types when your Wrangler configuration file changes.
Socket used by miniflare to communicate with Docker
Docker image name for the container egress interceptor sidecar