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

Patch Changes

• #1937 905fce4f Thanks @JacobMGEvans! - fix: fails to publish due to empty migrations
  After this change, wrangler init --from-dash will not attempt to add durable object migrations to wrangler.toml for Workers that don't have durable objects.

  fixes 🐛 BUG: A worker set up with init --from-dash fails to publish due to empty migrations #1854

• #1943 58a430f2 Thanks @cameron-robey! - chore: add env and ctx params to fetch in javascript example template

  Just like in the typescript templates, and the javascript template for scheduled workers, we include env and ctx as parameters to the fetch export. This makes it clearer where environment variables live.

• #1934 7ebaec1a Thanks @mrbbot! - Allow --experimental-local to be used with module workers

• #1939 5854cb69 Thanks @rozenmd! - fix: respect variable binding type when printing

  After this change, when printing the bindings it has access to, wrangler will correctly only add quotes around string variables, and serialize objects via JSON.stringify (rather than printing "[object Object]").

• #1953 20195479 Thanks @mrbbot! - Add --experimental-local support to unstable_dev

• #1930 56798155 Thanks @rozenmd! - fix: use node http instead of faye-websocket in proxy server

  We change how websockets are handled in the proxy server, fixing multiple issues of websocket behaviour, particularly to do with headers.

  In particular this fixes:

  • the protocol passed between the client and the worker was being stripped out by wrangler
  • wrangler was discarding additional headesr from websocket upgrade response
  • websocket close code and reason was not being propagated by wrangler