Bump the development-dependencies group across 1 directory with 8 updates

[dependabot]

Bumps the development-dependencies group with 8 updates in the / directory:

Package	From	To
@playwright/browser-chromium	1.49.0	1.49.1
@types/node	20.17.0	22.10.1
@vscode/test-cli	0.0.9	0.0.10
@vscode/test-web	0.0.56	0.0.65
esbuild	0.23.1	0.24.0
mocha	10.8.2	11.0.1
msw	2.2.13	2.6.8
typescript-eslint	8.17.0	8.18.0

Updates @playwright/browser-chromium from 1.49.0 to 1.49.1

Release notes

Sourced from @​playwright/browser-chromium'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 @types/node from 20.17.0 to 22.10.1

Commits

• See full diff in compare view

Updates @vscode/test-cli from 0.0.9 to 0.0.10

Changelog

Sourced from @​vscode/test-cli's changelog.

Changelog

TBA

• Fix bailing multiple configs on first failure (fixes #44)
• Fix extension install on Windows on modern Node versions (fixes #43)
• Normalize casing in paths (fixes #49)

Commits

• See full diff in compare view

Updates @vscode/test-web from 0.0.56 to 0.0.65

Release notes

Sourced from @​vscode/test-web's releases.

v0.0.65

Changes:

• #151: Set publishRequiresApproval to false in pipeline configuration
• #150: prepare 0.0.65

This list of changes was auto generated.

v0.0.64

Changes:

• #149: prepare 0.0.64
• #148: VS Code main has moved back to npm, we could catch it
• #147: apply learnings from wsl download fix

This list of changes was auto generated.

v0.0.63

Changes:

• #146: prepare 0.0.63
• #142: Bump path-to-regexp from 6.2.2 to 6.3.0

This list of changes was auto generated.

v0.0.62

Changes:

• #144: detect ESM from root package.json

This list of changes was auto generated.

v0.0.61

Changes:

• #143: prepare 0.61.0

This list of changes was auto generated.

v0.0.60

... (truncated)

Changelog

Sourced from @​vscode/test-web's changelog.

Changelog

0.0.58

• new option --commit to specify the build of VS Code to use. By default the latest build is used.

0.0.37

• new option --testRunnerDataDir to set the temporary folder for storing the VS Code builds used for running the tests

0.0.28

• new option --coi to enable cross origin isolation.

0.0.22

• new option --printServerLog replacing --hideServerLog.
• new option --browser replacing --browserType.

0.0.20

• new option --extensionId publisher.name[@prerelease] to include one or more extensions.

0.0.18

• new option --browserType none to start the server without opening a browser.

0.0.17

• new options --host and --port: If provided runs the server from the given host and port.
• new option --verbose to print out the browser console log.

0.0.16

• new option --sourcesPath: If provided, runs the server from VS Code sources at the given location.
• option --version is deprecated and replaced with quality. Supported values: stable, insiders. Instead of sources use --insiders.

0.0.14

• new option --extensionPath : A path pointing to a folder containing additional extensions to include. Argument can be provided multiple times.
• new option --permission: Permission granted to the opened browser: e.g. clipboard-read, clipboard-write. See full list of options here. Argument can be provided multiple times.
• new option --hideServerLog: If set, hides the server log. Defaults to true when an extensionTestsPath is provided, otherwise false.
• close server when browser is closed

0.0.9

• new option folderPath: A local folder to open VS Code on. The folder content will be available as a virtual file system and opened as workspace.

0.0.1 |

• Initial version

Commits

• be50e5f Set publishRequiresApproval to false in pipeline configuration (#151)
• 21c0ef4 prepare 0.0.65 (#150)
• 9a563fc prepare 0.0.64 (#149)
• 1cee314 VS Code main has migrated back to npm. (#148)
• f0ae7e3 apply learnings from wsl download fix (#147)
• 2c12f1c prepare 0.0.63 (#146)
• 46ef940 Bump path-to-regexp from 6.2.2 to 6.3.0 (#142)
• 8f7aac8 detect ESM from root package.json (#144)
• 4a353c7 prepare 0.61.0 (#143)
• c20a85f bring back d.ts file, prepare 0.0.60 (#141)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for @​vscode/test-web since your current version.

Updates esbuild from 0.23.1 to 0.24.0

Release notes

Sourced from esbuild's releases.

v0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

• Drop support for older platforms (#3902)

  This release drops support for the following operating system:

  • macOS 10.15 Catalina

  This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

  Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild --version
  

• Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

  Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

• Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

  TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

• Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

  Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

• Work around more issues with Deno 1.31+ (#3917)

  This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

  This fix was contributed by @​Joshix-1.

Changelog

Sourced from esbuild's changelog.

0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

• Drop support for older platforms (#3902)

  This release drops support for the following operating system:

  • macOS 10.15 Catalina

  This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

  Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild --version
  

• Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

  Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

• Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

  TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

• Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

  Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

• Work around more issues with Deno 1.31+ (#3917)

  This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

  This fix was contributed by @​Joshix-1.

Commits

• d34e79e publish 0.24.0 to npm
• 045a87f fix #3887: omit dead export warning for default
• 6e049b8 fix #3913: useDefineForClassFields and decorators
• 9c26f98 lower decorators for useDefineForClassFields #3913
• 46fdb68 fix #3898: incorrect cyclic tsconfig.json warning
• b500443 fix #3917: running esbuild cli with deno
• b125e62 run make update-compat-table
• 112b9aa fix #3915: stack overflow with yarn + tsconfig
• ed5a555 wasm: catch and rethrow stack overflows (#3915)
• 11d3196 fix #3902: update go 1.22.5 => 1.23.1
• Additional commits viewable in compare view

Updates mocha from 10.8.2 to 11.0.1

Release notes

Sourced from mocha's releases.

v11.0.1

11.0.1 (2024-12-02)

🌟 Features

• bumped glob dependency from 8 to 10 (#5250) (43c3157)

📚 Documentation

• fix examples for linkPartialObjects methods (#5255) (34e0e52)

v11.0.0 Prerelease

11.0.0 (2024-11-11)

⚠ BREAKING CHANGES

• adapt new engine range for Mocha 11 (#5216)

🌟 Features

• allow calling hook methods (#5231) (e3da641)

🩹 Fixes

• adapt new engine range for Mocha 11 (#5216) (80da25a)

📚 Documentation

• downgrade example/tests chai to 4.5.0 (#5245) (eac87e1)

Changelog

Sourced from mocha's changelog.

11.0.1 (2024-12-02)

🌟 Features

• bumped glob dependency from 8 to 10 (#5250) (43c3157)

📚 Documentation

• fix examples for linkPartialObjects methods (#5255) (34e0e52)

11.0.0 (2024-11-11)

⚠ BREAKING CHANGES

• adapt new engine range for Mocha 11 (#5216)

🌟 Features

• allow calling hook methods (#5231) (e3da641)

🩹 Fixes

• adapt new engine range for Mocha 11 (#5216) (80da25a)

📚 Documentation

• downgrade example/tests chai to 4.5.0 (#5245) (eac87e1)

Commits

• 4c558fb chore(main): release 11.0.1 (#5257)
• a5bd707 Release v11.0.1
• 43c3157 feat: bumped glob dependency from 8 to 10 (#5250)
• 34e0e52 docs: fix examples for linkPartialObjects methods (#5255)
• d3b2c38 chore(main): release 11.0.0 prerelease (#5241)
• 80da25a fix!: adapt new engine range for Mocha 11 (#5216)
• eac87e1 docs: downgrade example/tests chai to 4.5.0 (#5245)
• e3da641 feat: allow calling hook methods (#5231)
• See full diff in compare view

Updates msw from 2.2.13 to 2.6.8

Release notes

Sourced from msw's releases.

v2.6.8 (2024-12-07)

Bug Fixes

• setupServer: reapply interception after calling server.listen() after server.close() (#2383) (00da9cad4249b61732ee375d9dbefeb76028cc2b) @​kettanaito

v2.6.7 (2024-12-06)

Bug Fixes

• setupWorker: correctly delete internal accept header on passthrough (#2375) (3f40055b1d3814da4b30e5eb7555e09b1084798c) @​smouillour @​kettanaito

v2.6.6 (2024-11-22)

Bug Fixes

• types: support optional path parameters (#2368) (3b7b776e8c0de341185df4686a895c24326748d3) @​kettanaito

v2.6.5 (2024-11-16)

Bug Fixes

• support non-configurable responses (#2360) (5bf3e3bf5f9a6d32c79410c11abd539ec4c2ddc5) @​kettanaito

v2.6.4 (2024-11-10)

Bug Fixes

• prevent infinite loop when bypassing sendBeacon() requests (#2353) (2fa98c327acc51189f87789d9155c4ec57be2299) @​kettanaito
• remove the internal bypass request header before performing the request as-is in Node.js (#2353) (2fa98c327acc51189f87789d9155c4ec57be2299) @​kettanaito

v2.6.3 (2024-11-10)

Bug Fixes

• handleRequest: remove transformResponse option (#2351) (74c4a3a89970bbfc498c812790daef13766dea72) @​kettanaito

v2.6.2 (2024-11-07)

Bug Fixes

• update @bundled-es-modules/cookie to 2.0.1 (#2312) (c134352e8206b91740247f4f196767ab8a8eb921) @​kettanaito

v2.6.1 (2024-11-06)

Bug Fixes

• prevent instanceof handler check failures between different MSW versions (#2349) (28d26bd7fa585d76f9ca69a67dfa70a234450ed9) @​kettanaito

v2.6.0 (2024-10-29)

... (truncated)

Commits

• de3bedf chore(release): v2.6.8
• 00da9ca fix(setupServer): reapply interception after calling server.listen() after ...
• e8d748e chore(ci): fix broken restore cache key
• 6a2cf33 chore(release): v2.6.7
• 3f40055 fix(setupWorker): correctly delete internal accept header on passthrough (#...
• e61ee12 chore: use pnpm@9.14.0 for preview releases
• c86ad58 ci: run ci build related tests in parallel (#1907)
• bd5f47c chore: update to vitest@2 (#2379)
• 48e4c76 chore: update pnpm to v9.14.0 (#2211)
• 3cc9d9f chore(release): v2.6.6
• Additional commits viewable in compare view

Updates typescript-eslint from 8.17.0 to 8.18.0

Release notes

Sourced from typescript-eslint's releases.

v8.18.0

8.18.0 (2024-12-09)

🚀 Features

• eslint-plugin: [no-deprecated] report on super call of deprecated constructor (#10397)
• eslint-plugin: [switch-exhaustiveness-check] add support for "no default" comment (#10218)

🩹 Fixes

• typescript peer dependency (#10373)
• deps: update dependency eslint to v9.16.0 (#10471)
• eslint-plugin: [no-deprecated] check if a JSX attribute is deprecated (#10374)
• eslint-plugin: [no-base-to-string] handle more robustly when multiple toString() declarations are present for a type (#10432)
• eslint-plugin: [use-unknown-in-catch-callback-variable] only flag function literals (#10436)

❤️ Thank You

• Kim Sang Du @​developer-bandi
• Kirk Waiblinger @​kirkwaiblinger
• mdm317
• rtritto

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from typescript-eslint's changelog.

8.18.0 (2024-12-09)

🩹 Fixes

• typescript peer dependency (#10373)

❤️ Thank You

• rtritto

You can read about our versioning strategy and releases on our website.

Commits

• c60dbab chore(release): publish 8.18.0
• 4cb2cf8 fix: typescript peer dependency (#10373)
• See full diff 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

[dependabot]

Superseded by #1919.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.