chore(deps): bump miniflare and wrangler in /examples/cloudflare
Bumps miniflare to 3.20231030.4 and updates ancestor dependency wrangler. These dependencies need to be updated together.
Updates miniflare from 3.20231025.0 to 3.20231030.4
Release notes
Sourced from miniflare's releases.
[email protected]
Patch Changes
#4448
eb08e2dcThanks@mrbbot! - fix: include request url and headers in pretty error pageThis change ensures Miniflare's pretty error page includes the URL and headers of the incoming request, rather than Miniflare's internal request for the page.
[email protected]
Patch Changes
#4466
71fb0b86Thanks@mrbbot! - fix: ensure unused KV and Cache blobs cleaned upWhen storing data in KV, Cache and R2, Miniflare uses both an SQL database and separate blob store. When writing a key/value pair, a blob is created for the new value and the old blob for the previous value (if any) is deleted. A few months ago, we introduced a change that prevented old blobs being deleted for KV and Cache. R2 was unaffected. This shouldn't have caused any problems, but could lead to persistence directories growing unnecessarily as they filled up with garbage blobs. This change ensures garbage blobs are deleted.
Note existing garbage will not be cleaned up. If you'd like to do this, download this Node script (https://gist.github.com/mrbbot/68787e19dcde511bd99aa94997b39076). If you're using the default Wrangler persistence directory, run
node gc.mjs kv .wrangler/state/v3/kv <namespace_id_1> <namespace_id_2> ...andnode gc.mjs cache .wrangler/state/v3/cache default named:<cache_name_1> named:<cache_name_2> ...with each of your KV namespace IDs (not binding names) and named caches.#4550
63708a94Thanks@mrbbot! - fix: validateHostandOrginheaders where appropriate
HostandOriginheaders are now checked when connecting to the inspector and Miniflare's magic proxy. If these don't match what's expected, the request will fail.[email protected]
Patch Changes
#4505
1b348782Thanks@mrbbot! - fix: remove__STATIC_CONTENT_MANIFESTfrom module workerenvWhen using Workers Sites with a module worker, the asset manifest must be imported from the
__STATIC_CONTENT_MANIFESTvirtual module. Miniflare provided this module, but also erroneously added__STATIC_CONTENT_MANIFESTto theenvobject too. Whilst this didn't break anything locally, it could cause users to develop Workers that ran locally, but not when deployed. This change ensuresenvdoesn't contain__STATIC_CONTENT_MANIFEST.[email protected]
Minor Changes
#4348
be2b9cf5Thanks@mrbbot! - feat: add support for wrapped bindingsThis change adds a new
wrappedBindingsworker option for configuringworkerd's wrapped bindings. These allow custom bindings to be written as JavaScript functions accepting anenvparameter of "inner bindings" and returning the value to bind. For more details, refer to the API docs.#4341
d9908743Thanks@RamIdeas! - Added ahandleRuntimeStdiowhich enables wrangler (or any other direct use of Miniflare) to handle thestdoutandstderrstreams from the workerd child process. By default, if this option is not provided, the previous behaviour is retained which splits the streams into lines and callsconsole.log/console.error.[email protected]
Minor Changes
#4324
16cc2e92Thanks@penalosa! - Update to latest[email protected]#4322
8a25b7fbThanks@dario-piotrowicz! - addunsafeEvalBindingoption
... (truncated)
Changelog
Sourced from miniflare's changelog.
3.20231030.4
Patch Changes
#4448
eb08e2dcThanks@mrbbot! - fix: include request url and headers in pretty error pageThis change ensures Miniflare's pretty error page includes the URL and headers of the incoming request, rather than Miniflare's internal request for the page.
3.20231030.3
Patch Changes
#4466
71fb0b86Thanks@mrbbot! - fix: ensure unused KV and Cache blobs cleaned upWhen storing data in KV, Cache and R2, Miniflare uses both an SQL database and separate blob store. When writing a key/value pair, a blob is created for the new value and the old blob for the previous value (if any) is deleted. A few months ago, we introduced a change that prevented old blobs being deleted for KV and Cache. R2 was unaffected. This shouldn't have caused any problems, but could lead to persistence directories growing unnecessarily as they filled up with garbage blobs. This change ensures garbage blobs are deleted.
Note existing garbage will not be cleaned up. If you'd like to do this, download this Node script (https://gist.github.com/mrbbot/68787e19dcde511bd99aa94997b39076). If you're using the default Wrangler persistence directory, run
node gc.mjs kv .wrangler/state/v3/kv <namespace_id_1> <namespace_id_2> ...andnode gc.mjs cache .wrangler/state/v3/cache default named:<cache_name_1> named:<cache_name_2> ...with each of your KV namespace IDs (not binding names) and named caches.
#4550
63708a94Thanks@mrbbot! - fix: validateHostandOrginheaders where appropriate
HostandOriginheaders are now checked when connecting to the inspector and Miniflare's magic proxy. If these don't match what's expected, the request will fail.3.20231030.2
Patch Changes
#4505
1b348782Thanks@mrbbot! - fix: remove__STATIC_CONTENT_MANIFESTfrom module workerenvWhen using Workers Sites with a module worker, the asset manifest must be imported from the
__STATIC_CONTENT_MANIFESTvirtual module. Miniflare provided this module, but also erroneously added__STATIC_CONTENT_MANIFESTto theenvobject too. Whilst this didn't break anything locally, it could cause users to develop Workers that ran locally, but not when deployed. This change ensuresenvdoesn't contain__STATIC_CONTENT_MANIFEST.3.20231030.1
Minor Changes
#4348
be2b9cf5Thanks@mrbbot! - feat: add support for wrapped bindingsThis change adds a new
wrappedBindingsworker option for configuringworkerd's wrapped bindings. These allow custom bindings to be written as JavaScript functions accepting anenvparameter of "inner bindings" and returning the value to bind. For more details, refer to the API docs.
- #4341
d9908743Thanks@RamIdeas! - Added ahandleRuntimeStdiowhich enables wrangler (or any other direct use of Miniflare) to handle thestdoutandstderrstreams from the workerd child process. By default, if this option is not provided, the previous behaviour is retained which splits the streams into lines and callsconsole.log/console.error.3.20231030.0
Minor Changes
- #4324
16cc2e92Thanks@penalosa! - Update to latest[email protected]
... (truncated)
Commits
7506b24Version Packages (#4559)eb08e2dfix: include request url and headers in pretty error page (#4448)5e67ea1Version Packages (#4536)63708a9fix: validateHost/Originheaders in magic proxy and `InspectorProxyWorke...71fb0b8fix: ensure unused KV and Cache blobs cleaned up (#4466)97727deVersion Packages (#4495)311ffbd[wrangler] fix: changewrangler (pages) devto listen onlocalhostby def...1b34878fix: remove__STATIC_CONTENT_MANIFESTfrom module workerenv(#4505)f728503Version Packages (#4463)be2b9cffeat: add support for wrapped bindings (#4348)- Additional commits viewable in compare view
Updates wrangler from 3.15.0 to 3.22.1
Release notes
Sourced from wrangler's releases.
[email protected]
Patch Changes
#4635
5bc2699dThanks@mrbbot! - fix: prevent zombieworkerdprocessesPreviously, running
wrangler devwould leave behind "zombie"workerdprocesses. These processes prevented the same port being bound ifwrangler devwas restarted and sometimes consumed lots of CPU time. This change ensures allworkerdprocesses are killed whenwrangler devis shutdown.To clean-up existing zombie processes, run
pkill -KILL workerdon macOS/Linux ortaskkill /f /im workerd.exeon Windows.[email protected]
Minor Changes
#4632
a6a4e8a4Thanks@G4brym! - Deprecate constellation commands and add a warning when using the constellation binding#4130
e8a2a1d9Thanks@vkrasnov! - Added support for R2 Sippy incremental migration#4621
98dee932Thanks@rozenmd! - feat: add rows written/read in the last 24 hours towrangler d1 infooutput#4426
c628de59Thanks@OilyLime! - Improve queues list displaying as table, update queues API types[email protected]
Minor Changes
#4423
a94ef570Thanks@mrbbot! - feat: apply source mapping to logged stringsPreviously, Wrangler would only apply source mapping to uncaught exceptions. This meant if you caught an exception and logged its stack trace, the call sites would reference built JavaScript files as opposed to source files. This change looks for stack traces in logged messages, and tries to source map them.
Note source mapping is only applied when outputting logs.
Error#stackdoes not return a source mapped stack trace. This means the actual runtime value ofnew Error().stackand the output fromconsole.log(new Error().stack)may be different.Patch Changes
- #4511
66394681Thanks@huw! - Add 'took recursive isolate lock' warning to workerd output exceptions[email protected]
Minor Changes
#4522
c10bf0fdThanks@G4brym! - Add support for Workers AI in local mode#4571
3314dbdeThanks@penalosa! - feat: When Wrangler crashes, send an error report to Sentry to aid in debugging.When Wrangler's top-level exception handler catches an error thrown from Wrangler's application, it will offer to report the error to Sentry. This requires opt-in from the user every time.
Patch Changes
- #4577
4c85fe99Thanks@dario-piotrowicz! - During the R2 validation, showMAX_UPLOAD_SIZEerrors using MiB (consistently with the Cloudflare docs)
... (truncated)
Changelog
Sourced from wrangler's changelog.
3.22.1
Patch Changes
#4635
5bc2699dThanks@mrbbot! - fix: prevent zombieworkerdprocessesPreviously, running
wrangler devwould leave behind "zombie"workerdprocesses. These processes prevented the same port being bound ifwrangler devwas restarted and sometimes consumed lots of CPU time. This change ensures allworkerdprocesses are killed whenwrangler devis shutdown.To clean-up existing zombie processes, run
pkill -KILL workerdon macOS/Linux ortaskkill /f /im workerd.exeon Windows.3.22.0
Minor Changes
- #4632
a6a4e8a4Thanks@G4brym! - Deprecate constellation commands and add a warning when using the constellation binding
- #4130
e8a2a1d9Thanks@vkrasnov! - Added support for R2 Sippy incremental migration
- #4621
98dee932Thanks@rozenmd! - feat: add rows written/read in the last 24 hours towrangler d1 infooutput
- #4426
c628de59Thanks@OilyLime! - Improve queues list displaying as table, update queues API types3.21.0
Minor Changes
#4423
a94ef570Thanks@mrbbot! - feat: apply source mapping to logged stringsPreviously, Wrangler would only apply source mapping to uncaught exceptions. This meant if you caught an exception and logged its stack trace, the call sites would reference built JavaScript files as opposed to source files. This change looks for stack traces in logged messages, and tries to source map them.
Note source mapping is only applied when outputting logs.
Error#stackdoes not return a source mapped stack trace. This means the actual runtime value ofnew Error().stackand the output fromconsole.log(new Error().stack)may be different.Patch Changes
- #4511
66394681Thanks@huw! - Add 'took recursive isolate lock' warning to workerd output exceptions3.20.0
Minor Changes
#4571
3314dbdeThanks@penalosa! - feat: When Wrangler crashes, send an error report to Sentry to aid in debugging.When Wrangler's top-level exception handler catches an error thrown from Wrangler's application, it will offer to report the error to Sentry. This requires opt-in from the user every time.
Patch Changes
- #4577
4c85fe99Thanks@dario-piotrowicz! - During the R2 validation, showMAX_UPLOAD_SIZEerrors using MiB (consistently with the Cloudflare docs)
... (truncated)
Commits
6d3d46aVersion Packages (#4638)5bc2699fix: prevent zombieworkerdprocesses (#4635)35e8a5dVersion Packages (#4620)a6a4e8aDeprecate constellation commands and add a warning when using the constellati...e8a2a1dR2: Add Sippy support (#4130)cd4f63aAdd info aboutnode:${module}syntax for nodejs_compat (#4485)c628de5Improve listing of queues and update API types (#4426)98dee93[D1] add rows read/written towrangler d1 infooutput (#4621)912bfebVersion Packages (#4595)a94ef57[wrangler] feat: source map logged strings (#4423)- 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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| chronark-sdk-nextjs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Dec 29, 2023 7:40pm |