🦋 Changeset detected

Latest commit: 3943b7c

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/5357577961/npm-package-wrangler-3511

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/3511/npm-package-wrangler-3511

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/5357577961/npm-package-wrangler-3511 dev path/to/script.js

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/5357577961/npm-package-cloudflare-pages-shared-3511

Codecov Report

Merging #3511 (cbd19d8) into main (c43fc4e) will increase coverage by 0.02%.
The diff coverage is n/a.

❗ Current head cbd19d8 differs from pull request most recent head 3943b7c. Consider uploading reports for the commit 3943b7c to get more accurate results

@@            Coverage Diff             @@
##             main    #3511      +/-   ##
==========================================
+ Coverage   75.07%   75.10%   +0.02%     
==========================================
  Files         183      183              
  Lines       11083    11083              
  Branches     2917     2917              
==========================================
+ Hits         8321     8324       +3     
+ Misses       2762     2759       -3     

see 2 files with indirect coverage changes

I'm a bit concerned about the change in glob behaviour:

Globbing requires the --glob CLI option or glob option property to be set. (Removed in 4.0 and 4.1, opt-in support added in 4.2.)

Do we rely on that anywhere?

I'm a bit concerned about the change in glob behaviour:

Globbing requires the --glob CLI option or glob option property to be set. (Removed in 4.0 and 4.1, opt-in support added in 4.2.)

Do we rely on that anywhere?

Not that I could find. There is only really 2 places we use rimraf one is the direct script usage in Wrangler package.json and the 2nd is the ONLY one in the webpack package. @penalosa