Skip to content
Cloudflare Docs

Wrangler

Subscribe to RSS

2025-05-15

4.15.2

Patch Changes

2025-05-15

4.15.1

Patch Changes

  • #9248 07f4010 Thanks @vicb! - fix unenv version mismatch

  • #9219 ea71df3 Thanks @vicb! - bump unenv to 2.0.0-rc.17

  • #9246 d033a7d Thanks @edmundhung! - fix: strip CF-Connecting-IP header within fetch

    In v4.15.0, Miniflare began stripping the CF-Connecting-IP header via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches the fetch API to strip the header during local wrangler dev sessions as a temporary workaround until the underlying issue is resolved.

  • Updated dependencies [f61a08e, ea71df3, d033a7d]:

2025-05-13

4.15.0

Minor Changes

  • #8794 02f0699 Thanks @eastlondoner! - This adds support for more accurate types for service bindings when running wrangler types. Previously, running wrangler types with a config including a service binding would generate an Env type like this:

    interface Env {
    SERVICE_BINDING: Fetcher;
}

    This type was "correct", but didn't capture the possibility of using JSRPC to communicate with the service binding. Now, running wrangler types -c wrangler.json -c ../service/wrangler.json (the first config representing the current Worker, and any additional configs representing service bound Workers) will generate an Env type like this:

    interface Env {
    SERVICE_BINDING: Service<import("../service/src/index").Entrypoint>;
}

  • #8716 63a6504 Thanks @ItsWendell! - add --metafile flag to generate esbuild metadata file during build

  • #9122 f17ee08 Thanks @avenceslau! - Unhide wrangler workflows delete command

Patch Changes

2025-05-08

4.14.4

Patch Changes

  • #9124 d0d62e6 Thanks @dario-piotrowicz! - make that unstable_startWorker can correctly throw configuration errors

    make sure that unstable_startWorker can throw configuration related errors when:

    • the utility is called
    • the worker's setConfig is called with the throwErrors argument set to true

    additionally when an error is thrown when unstable_startWorker is called make sure that the worker is properly disposed (since, given the fact that it is not returned by the utility the utility's caller wouldn't have any way to dispose it themselves)

2025-05-07

4.14.3

Patch Changes

2025-05-06

4.14.2

Patch Changes

  • #9118 1cd30a5 Thanks @dario-piotrowicz! - fix: remove outdated js-doc comment for unstable_startDevWorker's entrypoint

  • #9120 11aa362 Thanks @dario-piotrowicz! - Add experimental_startMixedModeSession no-op utility

    This experimental utility has no effect. More details will be shared as we roll out its functionality.

  • #7423 2be85d7 Thanks @penalosa! - Make sure custom build logging output is more clearly signposted, and make sure it doesn't interfere with the interactive dev session output.

  • #9112 3fe85d4 Thanks @penalosa! - Warn if the Node.js version is below Node.js 20

2025-05-01

4.14.1

Patch Changes

  • #9085 cdc88d8 Thanks @petebacondarwin! - Do not include .wrangler and Wrangler config files in additional modules

    Previously, if you added modules rules such as **/*.js or **/*.json, specified no_bundle: true, and the entry-point to the Worker was in the project root directory, Wrangler could include files that were not intended, such as .wrangler/tmp/xxx.js or the Wrangler config file itself. Now these files are automatically skipped when trying to find additional modules by searching the file tree.

  • #9095 508a1a3 Thanks @petebacondarwin! - wrangler login put custom callback host and port into the auth URL

  • #9113 82e220e Thanks @dario-piotrowicz! - Add x-mixed-mode flag

    This experimental flag currently has no effect. More details will be shared as we roll out its functionality.

  • Updated dependencies [357d42a]:

2025-05-01

3.114.8

Patch Changes

  • #9086 a2a56c8 Thanks @petebacondarwin! - Do not include .wrangler and Wrangler config files in additional modules

    Previously, if you added modules rules such as **/*.js or **/*.json, specified no_bundle: true, and the entry-point to the Worker was in the project root directory, Wrangler could include files that were not intended, such as .wrangler/tmp/xxx.js or the Wrangler config file itself. Now these files are automatically skipped when trying to find additional modules by searching the file tree.

  • #9037 d0d0025 Thanks @CarmenPopoviciu! - fix: When generating Env types, set type of version metadata binding to WorkerVersionMetadata. This means it now correctly includes the timestamp field.

  • #9093 2f2f7ba Thanks @CarmenPopoviciu! - fix: Validate input file for Vectorize inserts

  • Updated dependencies [fc04292, a01adca]:

2025-04-29

4.14.0

Minor Changes

Patch Changes

2025-04-25

4.13.2

Patch Changes

2025-04-24

4.13.1

Patch Changes

2025-04-23

4.13.0

Minor Changes

  • #8640 5ce70bd Thanks @kentonv! - Add support for defining props on a Service binding.

    In your configuration file, you can define a service binding with props:

    {
    "services": [
        {
            "binding": "MY_SERVICE",
            "service": "some-worker",
            "props": { "foo": 123, "bar": "value" }
        }
    ]
}

    These can then be accessed by the callee:

    import { WorkerEntrypoint } from "cloudflare:workers";

export default class extends WorkerEntrypoint {
    fetch() {
        return new Response(JSON.stringify(this.ctx.props));
    }
}

  • #8771 0cfcfe0 Thanks @dario-piotrowicz! - feat: add config.keep_names option

    Adds a new option to Wrangler to allow developers to opt out of esbuild's keep_names option (https://esbuild.github.io/api/#keep-names). By default, Wrangler sets this to true

    This is something developers should not usually need to care about, but sometimes keep_names can create issues, and in such cases they will be now able to opt-out.

    Example wrangler.jsonc:

    {
    "name": "my-worker",
    "main": "src/worker.ts",
    "keep_names": false
}

Patch Changes

2025-04-22

4.12.1

Patch Changes

2025-04-22

3.114.7

Patch Changes

  • #8955 b7eba92 Thanks @workers-devprod! - When Wrangler encounters an error, if the Bun runtime is detected it will now warn users that Wrangler does not officially support Bun.

  • #8928 8bcb257 Thanks @dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands

    a validation check has recently been introduced to make wrangler error on deploy commands when an environment is specified and a redirected configuration is in use (the reason being that redirected configurations should not include any environment), this check is problematic with pages commands where the "production" environment is anyways set by default, to address this the validation check is being relaxed here on pages commands

2025-04-17

4.12.0

Minor Changes

  • #8316 69864b4 Thanks @gnekich! - introduce callback-host and callback-port param for wrangler login command

Patch Changes

2025-04-15

4.11.1

Patch Changes

2025-04-15

4.11.0

Minor Changes

Patch Changes

  • #8885 f2802f9 Thanks @CarmenPopoviciu! - Disambiguate the "No files to upload. Proceeding with deployment..." message

  • #8924 d2b44a2 Thanks @dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands

    a validation check has recently been introduced to make wrangler error on deploy commands when an environment is specified and a redirected configuration is in use (the reason being that redirected configurations should not include any environment), this check is problematic with pages commands where the "production" environment is anyways set by default, to address this the validation check is being relaxed here on pages commands

  • Updated dependencies [f5413c5]:

2025-04-14

3.114.6

Patch Changes

  • #8783 7bcf352 Thanks @petebacondarwin! - Improve error message when request to obtain membership info fails

    Wrangler now informs user that specific permission might be not granted when fails to obtain membership info. The same information is provided when Wrangler is unable to fetch user's email.

  • #8866 db673d6 Thanks @edmundhung! - improve error message when redirected config contains environments

    this change improves that validation error message that users see when a redirected config file contains environments, by:

    • cleaning the message formatting and displaying the offending environments in a list
    • prompting the user to report the issue to the author of the tool which has generated the config

  • #8600 91cf028 Thanks @workers-devprod! - add validation to redirected configs in regards to environments

    add the following validation behaviors to wrangler deploy commands, that relate to redirected configs (i.e. config files specified by .wrangler/deploy/config.json files):

    • redirected configs are supposed to be already flattened configurations without any environment (i.e. a build tool should generate redirected configs already targeting specific environments), so if wrangler encounters a redirected config with some environments defined it should error
    • given the point above, specifying an environment (--env=my-env) when using redirected configs is incorrect, so these environments should be ignored and a warning should be presented to the user

2025-04-10

4.10.0

Minor Changes

Patch Changes