build(deps-dev): bump wrangler from 3.96.0 to 3.99.0

[dependabot]

Bumps wrangler from 3.96.0 to 3.99.0.

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

• #7425 8757579 Thanks @​CarmenPopoviciu! - feat: Make DX improvements in wrangler dev --remote

  Workers + Assets projects have, in certain situations, a relatively degraded wrangler dev --remote developer experience, as opposed to Workers proper projects. This is due to the fact that, for Workers + Assets, we need to make extra API calls to:

  1. check for asset files changes
  2. upload the changed assets, if any

  This commit improves the wrangler dev --remote DX for Workers + Assets, for use cases when the User Worker/assets change while the API calls for previous changes are still in flight. For such use cases, we have put an exit early strategy in place, that drops the event handler execution of the previous changes, in favour of the handler triggered by the new changes.

• #7537 086a6b8 Thanks @​WillTaylorDev! - Provide validation around assets.experimental_serve_directly

• #7568 2bbcb93 Thanks @​WillTaylorDev! - Warn users when using smart placement with Workers + Assets and serve_directly is set to false

Patch Changes

• #7521 48e7e10 Thanks @​emily-shen! - feat: add experimental_patchConfig()

  experimental_patchConfig() can add to a user's config file. It preserves comments if its a wrangler.jsonc. However, it is not suitable for wrangler.toml with comments as we cannot preserve comments on write.

• Updated dependencies [1488e11, 7216835]:

  • [email protected]

[email protected]

Minor Changes

• #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

• #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

• #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

  Adds a Wrangler API to find and read a config file

• #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

  • Detect Pages & Workers CI
  • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

• #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

[email protected]

Minor Changes

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.99.0

Minor Changes

• #7425 8757579 Thanks @​CarmenPopoviciu! - feat: Make DX improvements in wrangler dev --remote

  Workers + Assets projects have, in certain situations, a relatively degraded wrangler dev --remote developer experience, as opposed to Workers proper projects. This is due to the fact that, for Workers + Assets, we need to make extra API calls to:

  1. check for asset files changes
  2. upload the changed assets, if any

  This commit improves the wrangler dev --remote DX for Workers + Assets, for use cases when the User Worker/assets change while the API calls for previous changes are still in flight. For such use cases, we have put an exit early strategy in place, that drops the event handler execution of the previous changes, in favour of the handler triggered by the new changes.

• #7537 086a6b8 Thanks @​WillTaylorDev! - Provide validation around assets.experimental_serve_directly

• #7568 2bbcb93 Thanks @​WillTaylorDev! - Warn users when using smart placement with Workers + Assets and serve_directly is set to false

Patch Changes

• #7521 48e7e10 Thanks @​emily-shen! - feat: add experimental_patchConfig()

  experimental_patchConfig() can add to a user's config file. It preserves comments if its a wrangler.jsonc. However, it is not suitable for wrangler.toml with comments as we cannot preserve comments on write.

• Updated dependencies [1488e11, 7216835]:

  • [email protected]

3.98.0

Minor Changes

• #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

• #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

• #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

  Adds a Wrangler API to find and read a config file

• #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

  • Detect Pages & Workers CI
  • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

• #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

3.97.0

... (truncated)

Commits

• aa9ec0f Version Packages (#7595)
• 2bbcb93 Add warning for smart placement w/assets (#7568)
• 1488e11 chore(deps): bump the workerd-and-workers-types group across 1 directory with...
• 8757579 feat(wrangler): DX improvements for wrangler dev --remote (#7425)
• 48e7e10 feat: add experimental_patchConfig (#7521)
• 086a6b8 Provide validation around experimental_serve_directly usage (#7537)
• c4cf040 Version Packages (#7574)
• 8def8c9 Revert "feat: add support for custom unenv resolve path" (#7583)
• c74195c chore(wrangler): Fix failing e2e tests (#7585)
• fb819f9 feat: add experimental_readRawConfig() (#7573)
• Additional commits viewable 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)