Skip to content

Releases: cloudflare/workers-sdk

create-cloudflare@2.0.13

18 Jul 17:34
f7ae0ea
Compare
Choose a tag to compare

Patch Changes

@cloudflare/pages-shared@0.7.0

18 Jul 17:34
f7ae0ea
Compare
Choose a tag to compare

Minor Changes

wrangler@3.2.0

11 Jul 19:00
1deda0f
Compare
Choose a tag to compare

Minor Changes

  • #3583 78ddb8de Thanks @penalosa! - Upgrade Miniflare (and hence workerd) to v3.20230710.0.

  • #3426 5a74cb55 Thanks @matthewdavidrodgers! - Prefer non-force deletes unless a Worker is a dependency of another.

    If a Worker is used as a service binding, a durable object namespace, an outbounds for a dynamic dispatch namespace, or a tail consumer, then deleting that Worker will break those existing ones that depend upon it. Deleting with ?force=true allows you to delete anyway, which is currently the default in Wrangler.

    Force deletes are not often necessary, however, and using it as the default has unfortunate consequences in the API. To avoid them, we check if any of those conditions exist, and present the information to the user. If they explicitly acknowledge they're ok with breaking their other Workers, fine, we let them do it. Otherwise, we'll always use the much safer non-force deletes. We also add a "--force" flag to the delete command to skip the checks and confirmation and proceed with ?force=true

Patch Changes

  • #3585 e33bb44a Thanks @mrbbot! - fix: register middleware once for module workers

    Ensure middleware is only registered on the first request when using module workers.
    This should prevent stack overflows and slowdowns when making large number of requests to wrangler dev with infrequent reloads.

  • #3547 e16d0272 Thanks @jspspike! - Fixed issue with wrangler dev not finding imported files. Previously when wrangler dev would automatically reload on any file changes, it would fail to find any imported files.

wranglerjs-compat-webpack-plugin@0.0.8

06 Jul 16:38
38fba4f
Compare
Choose a tag to compare

wrangler@3.1.2

06 Jul 16:38
38fba4f
Compare
Choose a tag to compare

Patch Changes

  • #3529 bcdc1fe5 Thanks @jspspike! - Support https in wrangler dev local mode

  • #3541 09f317d4 Thanks @GregBrimble! - chore: Bump miniflare@3.0.2

  • #3497 c5f3bf45 Thanks @evanderkoogh! - Refactor dev-only checkedFetch check from a method substitution to a JavaScript Proxy to be able to support Proxied global fetch function.

  • #3403 8d1521e9 Thanks @Cherry! - fix: wrangler generate will now work cross-device. This is very common on Windows install that use C:/ for the OS and another drive for user files.

create-cloudflare@2.0.11

06 Jul 16:38
38fba4f
Compare
Choose a tag to compare

Patch Changes

  • #3465 528cc0fc Thanks @jculvey! - Improvements to the project name selection prompt.

  • #3500 c43fc4e8 Thanks @jculvey! - Fix the output of the --version flag

  • #3343 cc9ced83 Thanks @petebacondarwin! - fix: use a valid compatibility date for worker templates

    Previously, we changed wrangler.toml to use the current date for the
    compatibility_date setting in wrangler.toml when generating workers.
    But this is almost always going to be too recent and results in a warning.

    Now we look up the most recent compatibility date via npm on the workerd
    package and use that instead.

    Fixes #2385

  • #3516 941764d0 Thanks @petebacondarwin! - fix: ensure the Angular fetch handler returns a "real" promise to Cloudflare

    Angular employs the Zone.js library to patch potentially async operations so that
    it can trigger change detection reliably. But in order to do this, it swaps out
    the native Promise with a ZoneAwarePromise class.

    The Cloudflare runtime (i.e. workerd) does runtime checks on the value returned
    from the fetch() handler, expecting it to be a native Promise and fails if not.

    This fix ensures that the actual object returned from the fetch() is actually a
    native Promise. We don't need to stop Angular using ZoneAwarePromises elsewhere.

  • #3486 436f752d Thanks @Cherry! - fix: use wrangler deploy command for deploying applications instead of the deprecated wrangler publish

@cloudflare/pages-shared@0.5.3

06 Jul 16:38
38fba4f
Compare
Choose a tag to compare

Patch Changes

wrangler@3.1.1

20 Jun 19:30
881ea7b
Compare
Choose a tag to compare

Patch Changes

  • #3498 fddffdf0 Thanks @GregBrimble! - fix: Prevent wrangler pages dev from serving asset files outside of the build output directory

  • #3431 68ba49a8 Thanks @Cherry! - fix: allow context.data to be overriden in Pages Functions

  • #3414 6b1870ad Thanks @rozenmd! - fix: in D1, lift error.cause into the error message

    Prior to this PR, folks had to console.log the error.cause property to understand why their D1 operations were failing. With this PR, error.cause will continue to work, but we'll also lift the cause into the error message.

  • #3483 a9349a89 Thanks @petebacondarwin! - fix: ensure that the script name is passed through to C3 from wrangler init

  • #3359 5eef992f Thanks @RamIdeas! - wrangler init ... -y now delegates to C3 without prompts (respects the -y flag)

  • #3434 4beac418 Thanks @rozenmd! - fix: add the number of read queries and write queries in the last 24 hours to the d1 info command

  • #3454 a2194043 Thanks @mrbbot! - chore: upgrade miniflare to 3.0.1

    This version ensures root CA certificates are trusted on Windows.
    It also loads extra certificates from the NODE_EXTRA_CA_CERTS environment variable,
    allowing wrangler dev to be used with Cloudflare WARP enabled.

  • #3485 e8df68ee Thanks @GregBrimble! - feat: Allow setting a D1 database ID when using wrangler pages dev by providing an optional =<ID> suffix to the argument like --d1 BINDING_NAME=database-id

create-cloudflare@2.0.10

20 Jun 19:30
881ea7b
Compare
Choose a tag to compare

Patch Changes

  • #3345 42f7eb81 Thanks @jculvey! - Use pnpm dlx instead of pnpx for versions of pnpm that support it

  • #3435 23be8025 Thanks @sdnts! - Updated wrangler.toml for Workers projects generated by create-cloudflare

  • #3496 91135e02 Thanks @petebacondarwin! - fix: ensure that default project name can be used

    If you hit enter when asked for the name of the project, you expect it
    to use the default value. But the project name validation was then failing
    as it was receiving undefined for the value of the input rather than the
    default value.

    Now the validator will be passed the default if no value was provided.

  • #3474 a72dc0a1 Thanks @elithrar! - Add new Queues and Scheduled (Cron Trigger) Worker templates.

  • #3446 ca0bd174 Thanks @admah! - refactor: rename simple template to hello-world in create-cloudflare package

    This change describes the "hello-world" template more accurately.
    Also, new e2e tests have been added to validate that Workers templates are created correctly.

  • #3359 5eef992f Thanks @RamIdeas! - wrangler init ... -y now delegates to C3 without prompts (respects the -y flag)

@cloudflare/pages-shared@0.5.2

20 Jun 19:30
881ea7b
Compare
Choose a tag to compare

Patch Changes

  • #3454 a2194043 Thanks @mrbbot! - chore: upgrade miniflare to 3.0.1

    This version ensures root CA certificates are trusted on Windows.
    It also loads extra certificates from the NODE_EXTRA_CA_CERTS environment variable,
    allowing wrangler dev to be used with Cloudflare WARP enabled.