Bump wrangler from 2.0.15 to 2.0.28

[dependabot]

Bumps wrangler from 2.0.15 to 2.0.28.

Release notes

Sourced from wrangler's releases.

wrangler@2.0.28

Patch Changes

• #1725 eb75413e Thanks @​threepointone! - rename: worker_namespaces / dispatch_namespaces

  The Worker-for-Platforms team would like to rename this field to more closely match what it's called internally. This fix does a search+replace on this term. This feature already had an experimental warning, and no one's using it at the moment, so we're not going to add a warning/backward compat for existing customers.

• #1736 800f8553 Thanks @​threepointone! - fix: do not delete previously defined plain_text/json bindings on publish

  Currently, when we publish a worker, we delete an pre-existing bindings if they're not otherwise defined in wrangler.toml, and overwrite existing ones. But folks may be deploying with wrangler, and changing environment variables on the fly (like marketing messages, etc). It's annoying when deploying via wrangler blows away those values.

  This patch fixes one of those issues. It will not delete any older bindings that are not in wrangler.toml. It still does overwrite existing vars, but at least this gives a way for developers to have some vars that are not blown away on every publish.

• #1726 0b83504c Thanks @​GregBrimble! - fix: Multiworker and static asset dev bug preventing both from being used

  There was previously a collision on the generated filenames which resulted in the generated scripts looping and crashing in Miniflare with error code 7. By renaming one of the generated files, this is avoided.

• #1718 02f1fe9b Thanks @​threepointone! - fix: use config.dev.ip when provided

  Because we'd used a default for 0.0.0.0 for the --ip flag, wrangler dev was overriding the value specified in wrangler.toml under dev.ip. This fix removes the default value (since it's being set when normalising config anyway).

  Fixes cloudflare/wrangler2#1714

• #1727 3f9e8f63 Thanks @​rozenmd! - fix: refresh token when we detect that the preview session has expired (error code 10049)

  When running wrangler dev, from time to time the preview session token would expire, and the dev server would need to be manually restarted. This fixes this, by refreshing the token when it expires.

  Closes #1446

• #1730 27ad80ee Thanks @​threepointone! - feat: --var name:value and --define name:value

  This enables passing values for [vars] and [define] via the cli. We have a number of usecases where the values to be injected during dev/publish aren't available statically (eg: a version string, some identifier for 3p libraries, etc) and reading those values only from wrangler.toml isn't good ergonomically. So we can now read those values when passed through the CLI.

  Example: add a var during dev: wrangler dev --var xyz:123 will inject the var xyz with string "123"

  (note, only strings allowed for --var)

  substitute a global value: wrangler dev --define XYZ:123 will replace every global identifier XYZ with the value 123.

  The same flags also work with wrangler publish.

  Also, you can use actual environment vars in these commands. e.g.: wrangler dev --var xyz:$XYZ will set xyz to whatever XYZ has been set to in the terminal environment.

• #1700 d7c23e49 Thanks @​penalosa! - Closes #1505 by extending wrangler tail to allow for passing worker routes as well as worker script names.

... (truncated)

Commits

• 85bf2f3 Version Packages (#1719)
• 2b847a2 Revert "Add support for 'export default { fetch() }' in Pages Functions"
• c964685 Add support for 'export default { fetch() }' in Pages Functions
• 27ad80e feat: --var name:value and --define name:value (#1730)
• 800f855 fix: do not delete previously defined plain_text/json bindings on publish (#1...
• 6f6e0d2 chore: update busboy's version in package-lock.json
• 1379897 fix: implement busboy to handle formData parsing (#1733)
• fbfc24d chore: dedupe running publish.test tests twice (#1728)
• eb75413 rename: worker_namespaces / dispatch_namespaces (#1725)
• 3f9e8f6 fix: rerun useEffect when we detect error code 10049 (#1727)
• 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #13.