[Docs Site] Bump wrangler from 3.99.0 to 3.100.0

[dependabot]

Bumps wrangler from 3.99.0 to 3.100.0.

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

• #7604 6c2f173 Thanks @​CarmenPopoviciu! - feat: Capture Workers with static assets in the telemetry data

  We want to measure accurately what this number of Workers + Assets projects running in remote mode is, as this number will be a very helpful data point down the road, when more decisions around remote mode will have to be taken.

  These changes add this kind of insight to our telemetry data, by capturing whether the command running is in the context of a Workers + Assets project.

  N.B. With these changes in place we will be capturing the Workers + Assets context for all commands, not just wrangler dev --remote.

Patch Changes

• #7581 cac7fa6 Thanks @​vicb! - chore(wrangler): update unenv dependency version

  unenv now uses the workerd implementation on node:dns See the unjs/unenv#376

• #7625 d8fb032 Thanks @​vicb! - feat(wrangler): use unenv builtin dependency resolution

  Moving away from require.resolve() to handle unenv aliased packages. Using the unenv builtin resolution will allow us to drop the .cjs file from the preset and to override the base path so that we can test the dev version of the preset.

• #7533 755a27c Thanks @​danielgek! - Add warning about the browser rendering not available on local

• #7614 8abb43f Thanks @​vicb! - chore(wrangler): update unenv dependency version

  The updated unenv contains a fix for the module resolution, see unjs/unenv#378. That bug prevented us from using unenv module resolution, see cloudflare/workers-sdk#7583.

• Updated dependencies [b4e0af1]:

  • [email protected]

Changelog

Sourced from wrangler's changelog.

3.100.0

Minor Changes

• #7604 6c2f173 Thanks @​CarmenPopoviciu! - feat: Capture Workers with static assets in the telemetry data

  We want to measure accurately what this number of Workers + Assets projects running in remote mode is, as this number will be a very helpful data point down the road, when more decisions around remote mode will have to be taken.

  These changes add this kind of insight to our telemetry data, by capturing whether the command running is in the context of a Workers + Assets project.

  N.B. With these changes in place we will be capturing the Workers + Assets context for all commands, not just wrangler dev --remote.

Patch Changes

• #7581 cac7fa6 Thanks @​vicb! - chore(wrangler): update unenv dependency version

  unenv now uses the workerd implementation on node:dns See the unjs/unenv#376

• #7625 d8fb032 Thanks @​vicb! - feat(wrangler): use unenv builtin dependency resolution

  Moving away from require.resolve() to handle unenv aliased packages. Using the unenv builtin resolution will allow us to drop the .cjs file from the preset and to override the base path so that we can test the dev version of the preset.

• #7533 755a27c Thanks @​danielgek! - Add warning about the browser rendering not available on local

• #7614 8abb43f Thanks @​vicb! - chore(wrangler): update unenv dependency version

  The updated unenv contains a fix for the module resolution, see unjs/unenv#378. That bug prevented us from using unenv module resolution, see cloudflare/workers-sdk#7583.

• Updated dependencies [b4e0af1]:

  • [email protected]

Commits

• a5725bd Version Packages (#7608)
• 547e8f8 Update telemetry doc to include data captured about the worker (#7691)
• d8fb032 feat(wrangler): use unenv bulitin dependency resolution (#7625)
• f5b3fb5 remove old assets remote check (#7675)
• 755a27c Add Warning about browser rendering when running locally (#7533)
• b4e0af1 chore(deps): bump the workerd-and-workers-types group across 1 directory with...
• 8abb43f chore(wrangler): update unenv dependency version (#7614)
• cac7fa6 Update unenv preset (#7581)
• 6c2f173 feat(wrangler): Capture Workers with static assets in the telemetry data (#7604)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[holopin-bot]

Congratulations @dependabot[bot], the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm5qr5i2f74760cjys3ilrnws

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!