chore(deps-dev): bump @playwright/test from 1.62.1 to 1.63.0

[dependabot]

Bumps @playwright/test from 1.62.1 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

[github-actions]

Redux Build System — CI Report

npm · commit b7d1c25

Operation	Status	Summary	Time
audit	❌	1 high · 1 moderate	0.9s
format-check	❌	60 format · 33 import order	0.5s
lint	❌	24 errors, 41 warnings	7.3s
typecheck	⏭️	no tsconfig.json	—
unit-test	⏭️	no test script in package.json	—
build	✅	built local/redux_gui:ci · 235MB	52.4s
integration-test	❌	1 failed · 3 passed	17.7s
push	⛔	not run — integration-test failed	—

Overall: ❌ 1 passed · 4 failed · 2 skipped · 1 blocked

❌ audit — 1 high · 1 moderate

Severity	Location	Rule	Message
high	svgo@3.0.0 - 3.3.4	GHSA-2p49-hgcm-8545	SVGO removeScripts plugin leaves some executable scripts intact
moderate	baseline-browser-mapping@>=2.0.0 <2.11.0	GHSA-w5vr-8v7q-w6rv	baseline-browser-mapping process termination on invalid input causes denial of service

❌ format-check — 60 format · 33 import order

Severity	Location	Rule	Message
error	Tools/Constants.js	format	needs formatting
error	Tools/ProblemInstanceParser.js	format	needs formatting
error	biome.json	format	needs formatting
error	components/ContributorCard.js	format	needs formatting
error	components/Quantum/QuantumCircuitVisualizer.js	assist/source/organizeImports	Sort these imports.
error	components/Quantum/QuantumCircuitVisualizer.js	format	needs formatting
error	components/Quantum/circuitUtils.js	format	needs formatting
error	components/Visualization/Graphvisualization.js	format	needs formatting
error	components/Visualization/GraphvizWrapper.js	assist/source/organizeImports	Sort these imports.
error	components/Visualization/QuantumCircuitVis.js	assist/source/organizeImports	Sort these imports.
error	components/Visualization/QuantumCircuitVis.js	format	needs formatting
error	components/Visualization/ReducedVisualization.js	format	needs formatting
error	components/Visualization/constants/VisColors.js	format	needs formatting
error	components/Visualization/constants/VisColorsArray.js	assist/source/organizeImports	Sort the exported names.
error	components/Visualization/constants/VisColorsArray.js	format	needs formatting
error	components/Visualization/openqasmToQText.js	format	needs formatting
error	components/Visualization/svgs/DynamicTableSvgReact.js	format	needs formatting
error	components/Visualization/svgs/LaTeXGraphSvgReact.js	format	needs formatting
error	components/Visualization/svgs/No_Viz_SVG.js	assist/source/organizeImports	Sort these imports.
error	components/Visualization/svgs/No_Viz_SVG.js	format	needs formatting
			… and 74 more

❌ lint — 24 errors, 41 warnings

Severity	Location	Rule	Message
error	components/Visualization/QuantumCircuitVis.js:152	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/hooks/ProblemProvider/Problem.js:51	no-undef	'requestInfo' is not defined.
error	components/hooks/ProblemProvider/Problem.js:73	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/hooks/ProblemProvider/Reducer.js:132	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/hooks/ProblemProvider/Reducer.js:152	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/hooks/ProblemProvider/Reducer.js:171	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/hooks/ProblemProvider/Reducer.js:190	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/hooks/ProblemProvider/Reducer.js:211	react-hooks/immutability	Error: Cannot access variable before it is declared
error	components/hooks/ProblemProvider/Reducer.js:215	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/hooks/ProblemProvider/Reducer.js:51	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/hooks/ProblemProvider/Reducer.js:74	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/hooks/ProblemProvider/Solver.js:122	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/hooks/ProblemProvider/Solver.js:24	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/hooks/ProblemProvider/Verifier.js:87	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/pageblocks/ProblemRowReact.js:177	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/pageblocks/ProblemRowReact.js:186	react-hooks/immutability	Error: This value cannot be modified
error	components/pageblocks/VerifyRowReact.js:52	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/pageblocks/VerifyRowReact.js:58	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/pageblocks/VisualizeRowReact.js:141	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
error	components/pageblocks/VisualizeRowReact.js:145	react-hooks/set-state-in-effect	Error: Calling setState synchronously within an effect can trigger cascading renders
			… and 45 more

[Trosper3]

Keeping playwright up to date will help with frontend site automation, testing, etc...