miniflare@3.20231030.4

Patch Changes

• #4448 eb08e2dc Thanks @mrbbot! - fix: include request url and headers in pretty error page

  This 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.

create-cloudflare@2.8.2

Patch Changes

• #4556 dcd3c582 Thanks @dependabot! - C3: Bumped create-vue from 3.8.0 to 3.9.0

• #4557 1a3e3ba4 Thanks @dependabot! - C3: Bumped create-svelte from 5.3.2 to 5.3.3

• #4558 ef03dc74 Thanks @dependabot! - C3: Bumped create-astro from 4.5.1 to 4.5.2

• #4564 d99bd421 Thanks @dependabot! - C3: Bumped @angular/create from 17.0.5 to 17.0.6

• #4565 be9a296d Thanks @dependabot! - C3: Bumped create-qwik from 1.2.19 to 1.3.0

• #4572 39d77323 Thanks @dependabot! - C3: Bumped gatsby from 5.12.11 to 5.12.12

• #4575 bb116f60 Thanks @dependabot! - C3: Bumped create-next-app from 14.0.3 to 14.0.4

• #4579 cccd56b8 Thanks @dario-piotrowicz! - Don't show cd instructions when the user is creating a project in the current directory

@cloudflare/pages-shared@0.11.4

Patch Changes

• Updated dependencies [eb08e2dc]:
  • miniflare@3.20231030.4

wrangler@3.19.0

Minor Changes

• #4547 86c81ff0 Thanks @mrbbot! - fix: listen on IPv4 loopback only by default on Windows

  Due to a known issue, workerd will only listen on the IPv4 loopback address 127.0.0.1 when it's asked to listen on localhost. On Node.js > 17, localhost will resolve to the IPv6 loopback address, meaning requests to workerd would fail. This change switches to using the IPv4 loopback address throughout Wrangler on Windows, while workerd#1408 gets fixed.

• #4535 29df8e17 Thanks @mrbbot! - Reintroduces some internal refactorings of wrangler dev servers (including wrangler dev, wrangler dev --remote, and unstable_dev()).

  These changes were released in 3.13.0 and reverted in 3.13.1 -- we believe the changes are now more stable and ready for release again.

  There are no changes required for developers to opt-in. Improvements include:

  • fewer 'address in use' errors upon reloads
  • upon config/source file changes, requests are buffered to guarantee the response is from the new version of the Worker

Patch Changes

• #4521 6c5bc704 Thanks @zebp! - fix: init from dash specifying explicit usage model in wrangler.toml for standard users

• #4550 63708a94 Thanks @mrbbot! - fix: validate Host and Orgin headers where appropriate

  Host and Origin headers 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.

• Updated dependencies [71fb0b86, 63708a94]:

  • miniflare@3.20231030.3

miniflare@3.20231030.3

Patch Changes

• #4466 71fb0b86 Thanks @mrbbot! - fix: ensure unused KV and Cache blobs cleaned up

  When 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> ... and node 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 63708a94 Thanks @mrbbot! - fix: validate Host and Orgin headers where appropriate

  Host and Origin headers 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.

create-cloudflare@2.8.1

Patch Changes

• #4538 a72f64c8 Thanks @dependabot! - C3: Bumped create-docusaurus from 3.0.0 to 3.0.1

@cloudflare/pages-shared@0.11.3

Patch Changes

• Updated dependencies [71fb0b86, 63708a94]:
  • miniflare@3.20231030.3

wrangler@3.18.0

Minor Changes

• #4532 311ffbd5 Thanks @mrbbot! - fix: change wrangler (pages) dev to listen on localhost by default

  Previously, Wrangler listened on all interfaces (*) by default. This change switches wrangler (pages) dev to just listen on local interfaces. Whilst this is technically a breaking change, we've decided the security benefits outweigh the potential disruption caused. If you need to access your dev server from another device on your network, you can use wrangler (pages) dev --ip * to restore the previous behaviour.

Patch Changes

• Updated dependencies [1b348782]:
  • miniflare@3.20231030.2

miniflare@3.20231030.2

Patch Changes

• #4505 1b348782 Thanks @mrbbot! - fix: remove __STATIC_CONTENT_MANIFEST from module worker env

  When using Workers Sites with a module worker, the asset manifest must be imported from the __STATIC_CONTENT_MANIFEST virtual module. Miniflare provided this module, but also erroneously added __STATIC_CONTENT_MANIFEST to the env object too. Whilst this didn't break anything locally, it could cause users to develop Workers that ran locally, but not when deployed. This change ensures env doesn't contain __STATIC_CONTENT_MANIFEST.

create-cloudflare@2.8.0

Minor Changes

• #4494 9bea4e32 Thanks @RamIdeas! - Change the default project type to the hello world worker script.

• #4525 294ca542 Thanks @jculvey! - C3: Use latest version of wrangler and @cloudflare/workers-types.

  Also updates the types entry of the project's tsconfig.json to use type definitions corresponding to the latest compatibility date.

Patch Changes

• #4445 652cc422 Thanks @petebacondarwin! - fix: ensure shell scripts work on Windows

  Our use of shell-quote was causing problems on Windows where it was
  escaping character (such as @) by placing a backslash in front.
  This made Windows think that such path arguments, were at the root.

  For example, npm install -D @cloudflare/workers-types was being converted to
  npm install -D \@cloudflare/workers-types, which resulted in errors like:

  npm ERR! enoent ENOENT: no such file or directory, open 'D:\@cloudflare\workers-types\package.json'
  

  Now we just rely directly on the Node.js spawn API to avoid any shell quoting
  concerns. This has resulted in a slightly less streamlined experience for people
  writing C3 plugins, but has the benefit that the developer doesn't have to worry
  about quoting spawn arguments.

  Closes #4282

• #4432 04a2d0ed Thanks @dependabot! - C3: Bumped create-solid from 0.3.9 to 0.3.10

• #4465 d79a68fd Thanks @dependabot! - C3: Bumped create-svelte from 5.2.0 to 5.3.1

• #4472 beed1575 Thanks @dependabot! - C3: Bumped nuxi from 3.9.1 to 3.10.0

• #4491 e6ddf8a7 Thanks @dependabot! - C3: Bumped create-qwik from 1.2.17 to 1.2.19

• #4504 3b5407a9 Thanks @dependabot! - C3: Bumped @angular/create from 17.0.1 to 17.0.3

• #4506 d8b5a01e Thanks @dependabot! - C3: Bumped gatsby from 5.12.9 to 5.12.11

• #4507 743d15fe Thanks @dependabot! - C3: Bumped create-remix from 2.2.0 to 2.3.1

• #4508 743df0af Thanks @dependabot! - C3: Bumped create-svelte from 5.3.1 to 5.3.2

• #4530 774b16c9 Thanks @dependabot! - C3: Bumped @angular/create from 17.0.3 to 17.0.5

• #4481 18a4dd92 Thanks @jculvey! - Minor improvements when using the --existing-script scriptName flag:

  • Format the type as "Pre-existing Worker (from Dashboard)"
  • Defaults the project name to scriptName

• #4445 652cc422 Thanks @petebacondarwin! - fix: update Nuxt template to work on Windows

  Rather than relying upon the non-Windows shell syntax to specify an environment variable,
  we now update the nuxt.config.ts files to include the cloudflare preset.

  Fixes #4285

• #4520 1b945a07 Thanks @petebacondarwin! - fix: ensure Angular alter-polyfill script works on Windows