chore(deps): update dependency wrangler to v3.80.0 - autoclosed #68
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.78.12
->3.80.0
Release Notes
cloudflare/workers-sdk (wrangler)
v3.80.0
Compare Source
Minor Changes
#6408
3fa846e
Thanks @RamIdeas! - feat: update the--experimental-dev-env
(shorthand:--x-dev-env
) flag to on-by-defaultIf you experience any issues, you can disable the flag with
--x-dev-env=false
. Please also let us know by opening an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose.Patch Changes
#6854
04a8fed
Thanks @penalosa! - chore: Include serialisedFormData
in debug logs#6879
b27d8cb
Thanks @petebacondarwin! - fix: the docs command should not crash if given search termsFixes a regression accidentally introduced by #3735.
#6873
b123f43
Thanks @zwily! - fix: reduce logging noise during wrangler dev with static assetsUpdates to static assets are accessible by passing in --log-level="debug" but otherwise hidden.
#6881
7ca37bc
Thanks @RamIdeas! - fix: custom builds outputting files in assets watched directory no longer cause the custom build to run again in an infinite loop#6872
b2d094e
Thanks @petebacondarwin! - fix: render a helpful build error if a Service Worker mode Worker has importsA common mistake is to forget to export from the entry-point of a Worker, which causes
Wrangler to infer that we are in "Service Worker" mode.
In this mode, imports to external modules are not allowed.
Currently this only fails at runtime, because our esbuild step converts these imports to an internal
__require()
call that throws an error.The error message is misleading and does not help the user identify the cause of the problem.
This is particularly tricky where the external imports are added by a library or our own node.js polyfills.
Fixes #6648
#6792
27e8385
Thanks @penalosa! - fix: Handle more module declaration cases#6838
7dbd0c8
Thanks @GregBrimble! - fix: Improve static asset upload messagingv3.79.0
Compare Source
Minor Changes
6009bb4
Thanks @RamIdeas! - feat: implement retries withinwrangler deploy
andwrangler versions upload
to workaround spotty network connections and service flakesPatch Changes
#6870
dc9039a
Thanks @penalosa! - fix: Includeworkerd
in the external dependecies of Wrangler to fix local builds.#6866
c75b0d9
Thanks @zwily! - fix: debounce restarting worker on assets dir file changesConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.