Bump the minor-and-patch group in /site with 3 updates

[dependabot]

Bumps the minor-and-patch group in /site with 3 updates: @playwright/test, prettier and wrangler.

Updates @playwright/test from 1.49.0 to 1.49.1

Release notes

Sourced from @​playwright/test's releases.

v1.49.1

Highlights

microsoft/playwright#33802 - [Bug]: Codegen's Clear button doesn't work if not recording microsoft/playwright#33806 - [Bug]: playwright hangs while waiting for pending navigations microsoft/playwright#33787 - [Bug]: VSC extension isn't capturing all entered text microsoft/playwright#33788 - [Regression]: Double clicking the steps in trace viewer doesn't filter actions microsoft/playwright#33772 - [Bug]: aria_snapshot generates invalid yaml when combined with an aria-label attribut microsoft/playwright#33791 - [Bug]: text input with number value raises "container is not iterable" with to_match_aria_snapshot microsoft/playwright#33644 - [Bug]: getByRole can't find element with the accessible name from label element when aria-labelledby is not valid microsoft/playwright#33660 - [Regression]: Unable to open Playwright UI in Dark Mode

Browser Versions

• Chromium 131.0.6778.33
• Mozilla Firefox 132.0
• WebKit 18.2

This version was also tested against the following stable channels:

• Google Chrome 130
• Microsoft Edge 130

Commits

• 88bc8af chore: mark v1.49.1 (#33921)
• 9e855d5 cherry-pick(#33821): fix(recorder): allow clearing when recording is disabled...
• 9365eb5 cherry-pick(#33834): fix: do not stall waiting for pending navigations after ...
• f92b233 cherry-pick(#33822): fix(codegen): do not reset current tool upon clearing hi...
• 008722b cherry-pick(#33797): fix(trace): in indexTree check isVisible before addi...
• 1dc8b3c cherry-pick(#33746): chore: pin typescript while vue-tsc is broken
• fbc770c cherry-pick(#33793): fix(aria): escape even more yaml (#33795)
• 1046fe0 cherry-pick(#33753): docs: update extensions doc for new headless
• 1781bf3 cherry-pick(#33706): docs: release notes for languages v1.49
• b52a210 cherry-pick(#33712): docs(python): add LocatorAssertions.NotToMatchAriaSnapshot
• Additional commits viewable in compare view

Updates prettier from 3.4.1 to 3.4.2

Release notes

Sourced from prettier's releases.

3.4.2

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.4.2

diff

Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @​tats-u)

Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.

<!-- Input (--prose-wrap=never) -->
C言
語
・
C++
・
Go
・
Rust
<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust
<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust

U+30A0 can be used as the replacement of the - in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン＝サーンス”).

Fix comments print on class methods with decorators (#16891 by @​fisker)

// Input
class A {
  @decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}
// Prettier 3.4.1
class A {
@​decorator
async /**
</tr></table>

... (truncated)

Commits

• cca9461 Release 3.4.2
• 572bebe Fix comments on class methods with decorators (#16891)
• 359c4f0 chore(deps): update dependency @​angular/compiler to v19.0.1 (#16903)
• 6470996 chore(deps): update dependency @​glimmer/syntax to v0.93.1 (#16904)
• e13614f Correct fit() for fill() (#16899)
• 10db357 Remove check on TSImportType.isTypeOf (#16892)
• ac46a4f Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796)
• d52e905 Add test for #16207 (#16890)
• a1e354d Clean changelog_unreleased
• 99875da Bump Prettier dependency to 3.4.1
• See full diff in compare view

Updates wrangler from 3.91.0 to 3.99.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

• #7425 8757579 Thanks @​CarmenPopoviciu! - feat: Make DX improvements in wrangler dev --remote

  Workers + Assets projects have, in certain situations, a relatively degraded wrangler dev --remote developer experience, as opposed to Workers proper projects. This is due to the fact that, for Workers + Assets, we need to make extra API calls to:

  1. check for asset files changes
  2. upload the changed assets, if any

  This commit improves the wrangler dev --remote DX for Workers + Assets, for use cases when the User Worker/assets change while the API calls for previous changes are still in flight. For such use cases, we have put an exit early strategy in place, that drops the event handler execution of the previous changes, in favour of the handler triggered by the new changes.

• #7537 086a6b8 Thanks @​WillTaylorDev! - Provide validation around assets.experimental_serve_directly

• #7568 2bbcb93 Thanks @​WillTaylorDev! - Warn users when using smart placement with Workers + Assets and serve_directly is set to false

Patch Changes

• #7521 48e7e10 Thanks @​emily-shen! - feat: add experimental_patchConfig()

  experimental_patchConfig() can add to a user's config file. It preserves comments if its a wrangler.jsonc. However, it is not suitable for wrangler.toml with comments as we cannot preserve comments on write.

• Updated dependencies [1488e11, 7216835]:

  • [email protected]

[email protected]

Minor Changes

• #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

• #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

• #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

  Adds a Wrangler API to find and read a config file

• #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

  • Detect Pages & Workers CI
  • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

• #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

[email protected]

Minor Changes

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.99.0

Minor Changes

• #7425 8757579 Thanks @​CarmenPopoviciu! - feat: Make DX improvements in wrangler dev --remote

  Workers + Assets projects have, in certain situations, a relatively degraded wrangler dev --remote developer experience, as opposed to Workers proper projects. This is due to the fact that, for Workers + Assets, we need to make extra API calls to:

  1. check for asset files changes
  2. upload the changed assets, if any

  This commit improves the wrangler dev --remote DX for Workers + Assets, for use cases when the User Worker/assets change while the API calls for previous changes are still in flight. For such use cases, we have put an exit early strategy in place, that drops the event handler execution of the previous changes, in favour of the handler triggered by the new changes.

• #7537 086a6b8 Thanks @​WillTaylorDev! - Provide validation around assets.experimental_serve_directly

• #7568 2bbcb93 Thanks @​WillTaylorDev! - Warn users when using smart placement with Workers + Assets and serve_directly is set to false

Patch Changes

• #7521 48e7e10 Thanks @​emily-shen! - feat: add experimental_patchConfig()

  experimental_patchConfig() can add to a user's config file. It preserves comments if its a wrangler.jsonc. However, it is not suitable for wrangler.toml with comments as we cannot preserve comments on write.

• Updated dependencies [1488e11, 7216835]:

  • [email protected]

3.98.0

Minor Changes

• #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

• #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

• #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

  Adds a Wrangler API to find and read a config file

• #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

  • Detect Pages & Workers CI
  • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

• #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

3.97.0

... (truncated)

Commits

• aa9ec0f Version Packages (#7595)
• 2bbcb93 Add warning for smart placement w/assets (#7568)
• 1488e11 chore(deps): bump the workerd-and-workers-types group across 1 directory with...
• 8757579 feat(wrangler): DX improvements for wrangler dev --remote (#7425)
• 48e7e10 feat: add experimental_patchConfig (#7521)
• 086a6b8 Provide validation around experimental_serve_directly usage (#7537)
• c4cf040 Version Packages (#7574)
• 8def8c9 Revert "feat: add support for custom unenv resolve path" (#7583)
• c74195c chore(wrangler): Fix failing e2e tests (#7585)
• fb819f9 feat: add experimental_readRawConfig() (#7573)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions