Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

wrangler@2.1.0

Minor Changes

• #1713 82451e9d Thanks @jspspike! - Tail now uses updated endpoint. Allows tailing workers that are above the normal "invocations per second" limit when using the --ip self filter.

Patch Changes

• #1745 1a13e483 Thanks @rozenmd! - fix: let users know when we'll use their proxy for requests

• #1782 cc43e3c4 Thanks @jahands! - fix: Update Pages test to assert version in package.json

  This test was asserting a hardcoded wrangler version which broke after release.

• #1786 1af49b68 Thanks @rozenmd! - fix: refactor unstable_dev to avoid race conditions with ports

  Prior to this change, wrangler would check to see if a port was available, do a bit more work, then try use that port when starting miniflare. With this change, we're using port 0 to tell Node to assign us a random free port.

  To make this change work, we had to do some plumbing so miniflare can tell us the host and port it's using, so we can call fetch against it.

• #1795 c17f6d3d Thanks @mrbbot! - Upgrade miniflare to 2.8

• #1788 152a1e81 Thanks @GregBrimble! - chore: Refactor 'wrangler pages dev' to use the same code as we do in production

  This will make our dev implementation an even closer simulation of production, and will make maintenance easier going forward.

• #1789 b21ee41a Thanks @JacobMGEvans! - fix: getMonth compatibility date
  Set correct month for compatibility_date when initializing a new Worker

  resolves 🐛 BUG: suggested compatibility_date when publishing has month off-by-one #1766

• #1694 3fb730a3 Thanks @yjl9903! - feat: starting pages dev server doesn't require command when proxy port provided

• #1729 ebb5b88f Thanks @JacobMGEvans! - feat: autogenerated config from dash

  Makes wrangler init's --from-dash option pull in data from Cloudflare's dashboard to generate a wrangler.toml file populated with configuration from an existing Worker.
  This is a first step towards making wrangler init more useful for folks who are already using Cloudflare's products on the Dashboard.

  related discussion RFC/Spec: `wrangler init` with flag `--from-dash` #1623
  resolves 🚀 Feature: Config auto-generate wrangler init --from-dash #1638

• #1781 603d0b35 Thanks @JacobMGEvans! - feat: Publish Origin Messaging
  feat: warn about potential conflicts during publish and init --from-dash.

  • If publishing to a worker that has been modified in the dashboard, warn that the dashboard changes will be overwritten.
  • When initializing from the dashboard, warn that future changes via the dashboard will not automatically appear in the local Worker config.

  resolves 🚀 Feature: Messaging when running publish & init --from-dash  #1737

• #1735 de29a445 Thanks @cameron-robey! - feat: new internal middleware

  A new way of registering middleware that gets bundled and executed on the edge.

  • the same middleware functions can be used for both modules workers and service workers
  • only requires running esbuild a fixed number of times, rather than for each middleware added