[dependabot]

Bumps the client-minor-and-patch group with 4 updates in the /clients directory: livekit-client, @playwright/test, @types/node and esbuild.

Updates livekit-client from 2.21.0 to 2.22.3

Release notes

Sourced from livekit-client's releases.

v2.22.3

Patch Changes

• fix: add code 1000 to onclose handler in WebSocketStream - #2086 (@​phaitonican)

• forward worker logs to main thread - #2078 (@​lukasIO)

• fix: don't reset mid track map on publisher answers with empty map - #2089 (@​lukasIO)

• Support simulcast for svc codecs (vp9/av1) - #2083 (@​cnderrauber)

v2.22.2

Patch Changes

• Fix the subscriber silently buffering remote ICE candidates after a reconnect - #2054 (@​xianshijing-lk)

  triggerIceRestart put the subscriber into restartingIce on every reconnect, but only setRemoteDescription clears that — and the server re-offers the subscriber only when the reconnect moved the participant to a different node. After an ordinary signal-only resume no offer arrives, so the flag stayed set for the lifetime of the transport and every subsequent remote candidate was queued instead of applied, leaving the subscriber unable to adopt any new network path the server proposed. The subscriber no longer enters that state: the server does not send candidates ahead of the offer that introduces them, so queueing them gains nothing.

• fix: track ws close with attemptId - #2069 (@​lukasIO)

• fix: ensure buffered events are flushed on signal reconnection - #2044 (@​lukasIO)

• fix: error on datastreams when chunks are missing - #2073 (@​lukasIO)

v2.22.1

Patch Changes

• Forward DisconnectReason to the ParticipantDisconnected event - #2055 (@​seonghunYang)

• chore: periodically log webrtc stats - #2064 (@​lukasIO)

• fix: enqueue signal requests until queue has been drained - #2061 (@​lukasIO)

• Add roomOptions.dataStream.maxPayloadByteLength to control max data stream size - #2060 (@​1egoman)

• chore: signalling state machine - #2046 (@​lukasIO)

• fix: catch unhandled ws signal errors - #2065 (@​lukasIO)

• Fix supportsAdaptiveStream always returning true by comparing typeof against the 'undefined' string. It now returns false in environments without ResizeObserver or IntersectionObserver. - #2059 (@​mrpmohiburrahman)

• Treat TokenSource JWTs without exp as expired, and still honor exp when nbf is absent - #2057 (@​SashaMIT)

• Convert internal exports to be external in examples/demo - #2067 (@​1egoman)

... (truncated)

Changelog

Sourced from livekit-client's changelog.

2.22.3

Patch Changes

• fix: add code 1000 to onclose handler in WebSocketStream - #2086 (@​phaitonican)

• forward worker logs to main thread - #2078 (@​lukasIO)

• fix: don't reset mid track map on publisher answers with empty map - #2089 (@​lukasIO)

• Support simulcast for svc codecs (vp9/av1) - #2083 (@​cnderrauber)

2.22.2

Patch Changes

• Fix the subscriber silently buffering remote ICE candidates after a reconnect - #2054 (@​xianshijing-lk)

  triggerIceRestart put the subscriber into restartingIce on every reconnect, but only setRemoteDescription clears that — and the server re-offers the subscriber only when the reconnect moved the participant to a different node. After an ordinary signal-only resume no offer arrives, so the flag stayed set for the lifetime of the transport and every subsequent remote candidate was queued instead of applied, leaving the subscriber unable to adopt any new network path the server proposed. The subscriber no longer enters that state: the server does not send candidates ahead of the offer that introduces them, so queueing them gains nothing.

• fix: track ws close with attemptId - #2069 (@​lukasIO)

• fix: ensure buffered events are flushed on signal reconnection - #2044 (@​lukasIO)

• fix: error on datastreams when chunks are missing - #2073 (@​lukasIO)

2.22.1

Patch Changes

• Forward DisconnectReason to the ParticipantDisconnected event - #2055 (@​seonghunYang)

• chore: periodically log webrtc stats - #2064 (@​lukasIO)

• fix: enqueue signal requests until queue has been drained - #2061 (@​lukasIO)

• Add roomOptions.dataStream.maxPayloadByteLength to control max data stream size - #2060 (@​1egoman)

• chore: signalling state machine - #2046 (@​lukasIO)

• fix: catch unhandled ws signal errors - #2065 (@​lukasIO)

• Fix supportsAdaptiveStream always returning true by comparing typeof against the 'undefined' string. It now returns false in environments without ResizeObserver or IntersectionObserver. - #2059 (@​mrpmohiburrahman)

... (truncated)

Commits

• 53dd840 Version Packages (#2088)
• 9b3ad5e fix: only apply map update in singlePC mode on answer (#2090)
• 0143077 align E2eeManager with logging pattern (#2081)
• 15931b8 finalization strategy for worker listeners (#2079)
• 8617f84 forward worker logs to main thread (#2078)
• 8054c66 fix: add code 1000 to onclose handler in WebSocketStream (#2086)
• ab7a827 fix: don't reset mid track map on publisher answers with empty map (#2089)
• 113d512 Support simulcast for svc codecs (vp9/av1) (#2083)
• ae32e31 chore(deps): update actions/checkout action to v6.1.0 (#2076)
• e775b6a chore(deps): update dependency jose to v6.2.9 (#2075)
• Additional commits viewable in compare view

Updates @playwright/test from 1.58.2 to 1.63.0

Release notes

Sourced from @​playwright/test's releases.

v1.63.0

🔒 Test locks

Tests that access a shared resource — an external service, a global account setting — can now declare a named lock. Tests that share a lock name never run concurrently, across files, workers and projects, while everything else keeps running in parallel:

test('update user settings', { lock: 'user-settings' }, async ({ page }) => {
  // never runs at the same time as other tests holding 'user-settings'
});

A test can hold multiple locks, and test.describe() accepts a lock for the whole group. Learn more about test locks.

🪟 Locate across frames

page.frameLocator() and frame.frameLocator() called without a selector search in any frame of the subtree, so you no longer need to locate the iframe first:

// Finds the button in any frame on the page.
await page.frameLocator().getByRole('button').click();

The rest of the locator resolves inside a single frame, just like a regular locator, and an error is thrown when it matches elements in several frames.

👁️ Visible-only locators

New locator.visible() returns a locator that matches only visible elements. It is the recommended replacement for the :visible CSS pseudo-class:

await page.locator('button').visible().click();

🧾 Step params and subtitles

Steps now carry structured data for reporters. Playwright API steps report the target locator and call arguments, and test.step() accepts subtitle and params options for your own steps:

await test.step('Login', async () => {
  // ...
}, { subtitle: 'as admin', params: { user: 'admin' } });

Reporters receive them via testStep.subtitle and testStep.params. For Playwright API

... (truncated)

Commits

• 1b025d7 chore: mark v1.63.0 (#42569)
• 0b9956d cherry-pick(#42568): docs(test): mark test.step subtitle option as since v1.63
• 13dbf10 cherry-pick(#42552): docs: release notes for v1.63
• e93b64e cherry-pick(#42566): feat(test): add subtitle option to test.step (#42567)
• 2b7a5f2 test: response.body() for content-encoding:identity (#42537)
• 648a67c fix(mcp): create parent directories for explicitly named files (#42540)
• 7894f56 docs(mcp): clarify how tool file names are resolved (#42538)
• 52900a1 devops: restore npm publishing from GitHub Actions (#42550)
• 8c47f59 docs(csharp): fix nonexistent method names in guide examples (#42507)
• bd6e552 chore(video): emit frames with real timestamps, drop frame number quantizatio...
• Additional commits viewable in compare view

Updates @types/node from 22.20.1 to 22.20.4

Commits

• See full diff in compare view

Updates esbuild from 0.28.1 to 0.28.2

Release notes

Sourced from esbuild's releases.

v0.28.2

• Fix tree shaking bug due to TypeScript import alias (#4507)

  This release fixes a bug that could cause esbuild to incorrectly tree-shake imports that are used in a TypeScript type alias under certain circumstances. Affected code uses a TypeScript-specific import assignment and looks something like this:

  import Base from './dep.js';
  import Alias = Base.SomeType;

• Fix CSS minification bug involving & (#4497)

  This release fixes a bug where esbuild's CSS minifier incorrectly removed a & when it was unsafe to do so. Here is an example:

  /* Original code */
  .a .b {
    & .b:not(& .c) {
      color: red;
    }
  }
  /* Old output (with --minify) */
  .a .b{.b:not(& .c){color:red}}
  /* New output (with --minify) */
  .a .b{& .b:not(& .c){color:red}}

  This should match <span class="a"><span class="b"><span class="b">yes</span></span></span> but not <span class="a"><span class="b">no</span></span>. The old output incorrectly matched both.

• Avoid overwriting input files without --allow-overwrite (#4484)

  For example: esbuild input.js --outfile=input.js tells esbuild to overwrite input.js with the output of running esbuild on it. This was supposed to already be prevented by default, but it accidentally regressed in version 0.17.0 and apparently didn't have any test coverage. The error message was being printed but the input file was still being overwritten. Oops.

  This release puts the original behavior back. With this release, esbuild should now actually avoid overwriting input files unless --allow-overwrite is explicitly present. This is done by not writing out any files when a build error is encountered.

• Fix incorrect code generated when using top-level await (#4498)

  Previously esbuild could generate code containing a syntax error in complex scenarios involving top-level await used in a dependency cycle. The problem was a missing async on one or more module wrapper closures. With this release, esbuild now uses a fixed-point iteration algorithm to correctly annotate all dependencies in the cycle as needing an async module wrapper.

• Fix a minification bug with lowered logical assignment operators (#4508)

  This release fixes a bug that could cause esbuild to generate incorrect code for logical assignment operators when lowering them to an older target environment. Specifically the lowering process requires duplicating the left-hand side, but esbuild incorrectly failed to count the duplicate as a new usage when the left-hand side is an identifier. That then caused the minifier to believe that the left-hand side was only used once and could attempt to incorrectly inline an initializer into the first usage. This bug has now been fixed:

  // Original code
  function foo() {
    let x
    bar(x ||= {})

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.28.2

• Fix tree shaking bug due to TypeScript import alias (#4507)

  This release fixes a bug that could cause esbuild to incorrectly tree-shake imports that are used in a TypeScript type alias under certain circumstances. Affected code uses a TypeScript-specific import assignment and looks something like this:

  import Base from './dep.js';
  import Alias = Base.SomeType;

• Fix CSS minification bug involving & (#4497)

  This release fixes a bug where esbuild's CSS minifier incorrectly removed a & when it was unsafe to do so. Here is an example:

  /* Original code */
  .a .b {
    & .b:not(& .c) {
      color: red;
    }
  }
  /* Old output (with --minify) */
  .a .b{.b:not(& .c){color:red}}
  /* New output (with --minify) */
  .a .b{& .b:not(& .c){color:red}}

  This should match <span class="a"><span class="b"><span class="b">yes</span></span></span> but not <span class="a"><span class="b">no</span></span>. The old output incorrectly matched both.

• Avoid overwriting input files without --allow-overwrite (#4484)

  For example: esbuild input.js --outfile=input.js tells esbuild to overwrite input.js with the output of running esbuild on it. This was supposed to already be prevented by default, but it accidentally regressed in version 0.17.0 and apparently didn't have any test coverage. The error message was being printed but the input file was still being overwritten. Oops.

  This release puts the original behavior back. With this release, esbuild should now actually avoid overwriting input files unless --allow-overwrite is explicitly present. This is done by not writing out any files when a build error is encountered.

• Fix incorrect code generated when using top-level await (#4498)

  Previously esbuild could generate code containing a syntax error in complex scenarios involving top-level await used in a dependency cycle. The problem was a missing async on one or more module wrapper closures. With this release, esbuild now uses a fixed-point iteration algorithm to correctly annotate all dependencies in the cycle as needing an async module wrapper.

• Fix a minification bug with lowered logical assignment operators (#4508)

  This release fixes a bug that could cause esbuild to generate incorrect code for logical assignment operators when lowering them to an older target environment. Specifically the lowering process requires duplicating the left-hand side, but esbuild incorrectly failed to count the duplicate as a new usage when the left-hand side is an identifier. That then caused the minifier to believe that the left-hand side was only used once and could attempt to incorrectly inline an initializer into the first usage. This bug has now been fixed:

  // Original code
  function foo() {
    let x

... (truncated)

Commits

• 609683d publish 0.28.2 to npm
• 11b1fe4 add to release notes
• ab50d91 css: fix green/blue channel swap in oklch gamut mapping (#4488)
• 04627b6 fix #4498: async TLA checks need a worklist
• 5c15177 disable gopls in the go folder
• fc2ee9b css: adjust parser to allow --foo: {...}
• 209db54 release notes for css nesting bugfix
• c625d31 fix #4497: preserve nested ampersands during minification (#4500)
• 34474e2 better isolation of current part in js parser
• 07f6e8c fix #4507: import assignment tree-shaking bug
• Additional commits viewable in compare view