Bump wrangler from 2.0.27 to 2.7.1

[dependabot]

Bumps wrangler from 2.0.27 to 2.7.1.

Release notes

Sourced from wrangler's releases.

wrangler@2.7.1

Patch Changes

• #2523 a5e9958c Thanks @​jahands! - fix: unstable_dev() experimental options incorrectly applying defaults

  A subtle difference when removing object-spreading of experimental unstable_dev() options caused wrangler pages dev interactivity to stop working. This switches back to object-spreading the passed in options on top of the defaults, fixing the issue.

wrangler@2.7.0

Minor Changes

• #2465 e1c2f5b9 Thanks @​JacobMGEvans! - After this PR, wrangler init --yes will generate a test for your new Worker project, using Vitest with TypeScript. When using wrangler init, and choosing to create a Typescript project, you will now be asked if Wrangler should write tests for you, using Vitest.

  This resolves issue #2436.

• #2333 71691421 Thanks @​markjmiller! - Remove the experimental binding warning from Dispatch Namespace since it is GA.

Patch Changes

• #2460 c2b2dfb8 Thanks @​rozenmd! - fix: resolve unstable_dev flakiness in tests by awaiting the dev registry

• #2439 616f8739 Thanks @​petebacondarwin! - fix(wrangler): do not login or read wrangler.toml when applying D1 migrations in local mode.

  When applying D1 migrations to a deployed database, it is important that we are logged in and that we have the database ID from the wrangler.toml. This is not needed for --local mode where we are just writing to a local SQLite file.

• #1869 917b07b0 Thanks @​petebacondarwin! - feat: enable Wrangler to target the staging API by setting WRANGLER_API_ENVIRONMENT=staging

  If you are developing Wrangler, or an internal Cloudflare feature, and during testing, need Wrangler to target the staging API rather than production, it is now possible by setting the WRANGLER_API_ENVIRONMENT environment variable to staging.

  This will update all the necessary OAuth and API URLs, update the OAuth client ID, and also (if necessary) acquire an Access token for to get through the firewall to the staging URLs.

• #2377 32686e42 Thanks @​mrbbot! - Fix ReferenceError when using wrangler dev --experimental-local in Node 16

• #2393 a6d24732 Thanks @​mrbbot! - Remove login requirement from wrangler dev --experimental-local

• #2502 6b7ebc8d Thanks @​mrbbot! - Upgrade miniflare to 2.11.0

... (truncated)

Changelog

Sourced from wrangler's changelog.

2.7.1

Patch Changes

• #2523 a5e9958c Thanks @​jahands! - fix: unstable_dev() experimental options incorrectly applying defaults

  A subtle difference when removing object-spreading of experimental unstable_dev() options caused wrangler pages dev interactivity to stop working. This switches back to object-spreading the passed in options on top of the defaults, fixing the issue.

2.7.0

Minor Changes

• #2465 e1c2f5b9 Thanks @​JacobMGEvans! - After this PR, wrangler init --yes will generate a test for your new Worker project, using Vitest with TypeScript. When using wrangler init, and choosing to create a Typescript project, you will now be asked if Wrangler should write tests for you, using Vitest.

  This resolves issue #2436.

• #2333 71691421 Thanks @​markjmiller! - Remove the experimental binding warning from Dispatch Namespace since it is GA.

Patch Changes

• #2460 c2b2dfb8 Thanks @​rozenmd! - fix: resolve unstable_dev flakiness in tests by awaiting the dev registry

• #2439 616f8739 Thanks @​petebacondarwin! - fix(wrangler): do not login or read wrangler.toml when applying D1 migrations in local mode.

  When applying D1 migrations to a deployed database, it is important that we are logged in and that we have the database ID from the wrangler.toml. This is not needed for --local mode where we are just writing to a local SQLite file.

• #1869 917b07b0 Thanks @​petebacondarwin! - feat: enable Wrangler to target the staging API by setting WRANGLER_API_ENVIRONMENT=staging

  If you are developing Wrangler, or an internal Cloudflare feature, and during testing, need Wrangler to target the staging API rather than production, it is now possible by setting the WRANGLER_API_ENVIRONMENT environment variable to staging.

  This will update all the necessary OAuth and API URLs, update the OAuth client ID, and also (if necessary) acquire an Access token for to get through the firewall to the staging URLs.

• #2377 32686e42 Thanks @​mrbbot! - Fix ReferenceError when using wrangler dev --experimental-local in Node 16

• #2393 a6d24732 Thanks @​mrbbot! - Remove login requirement from wrangler dev --experimental-local

• #2502 6b7ebc8d Thanks @​mrbbot! - Upgrade miniflare to 2.11.0

• #2485 4c0e2309 Thanks @​GregBrimble! - fix: Pages Plugin routing when mounted at the root of a project

  Previously, there was a bug which meant that Plugins mounted at the root of a Pages project were not correctly matching incoming requests. This change fixes that bug so Plugins mounted at the root should now correctly work.

• #2479 7b479b91 Thanks @​rozenmd! - fix: bump d1js

... (truncated)

Commits

• 90cf62e Version Packages (#2524)
• a5e9958 fix: unstable_dev() experimental options incorrectly applying defaults (#2523)
• e60dc90 Version Packages (#2394)
• 4dde0c3 Fix init --yes (#2520)
• e93063e fix(d1): ensure that migrations support compound statements (#2495)
• 58ab7ae Move \<ChooseAccount> to remote.tsx (#2510)
• 6b7ebc8 chore: upgrade miniflare to 2.11.0 (#2502)
• 415392a Update prebuilt yoga-layout from https://github.com/facebook/yoga (#2489)
• 95585ce Initial Ink removal (#2283)
• 4c0e230 Fix Pages Plugin routing (#2485)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by wrangler-publisher, a new releaser for wrangler since your current version.

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 #43.