@playwright/test
- 1.64.1 is the latest, published 14 October 2026.
- No known security advisory.
- 1.x: 128 releases since 9 June 2021, 5 in the last 90 days.
Releases in the last 90 days
Feed of releases and advisoriesEvery stable release, newest first. Notes are quoted as the maintainers published them.
1.64.1
14 October 2026[Bug]: _electron.launch intermittently loses a packaged app's first window since 1.64.0
Bug Fixes
[Bug]: _electron.launch intermittently loses a packaged app's first window since 1.64.0
[Regression]: Chromium 155+ aborts a preflighted cross-origin redirect whenever any route is registered (net::ERR_ABORTED)
1.64.0
7 October 20261.63.0
4 September 2026Tests that access a shared resource — an external service, a global account setting — can now declare a named lock.
Section of a shared release note
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
lockfor the whole group. Learn more about test locks.1.62.1
30 July 2026[Regression]: tsconfig "extends" bare specifier isn't resolved via node_modules walk-up like tsc (fatal since 1.62)
Bug Fixes
[Regression]: tsconfig "extends" bare specifier isn't resolved via node_modules walk-up like tsc (fatal since 1.62)
[Regression]: directory-form tsconfig project references ("path": "../pkg") fail to resolve (fatal since 1.62)
Accessibility snapshot drops button name when text is nested inside spans with aria-hidden SVG
[Regression]: page.evaluate() arg of a branded primitive type (string & { brand }) no longer type-checks since 1.62
[BUG]Image-type actionable elements are not presented in the snapshot.
1.62.0
24 July 2026New reporter.preprocess() hook runs after the configuration is resolved and before reporter.onBegin(), letting a reporter mark individual tests as skipped, excluded, fixed, or failing through a TestRun object:
Section of a shared release note
Custom test filtering with Reporter.preprocess()
New reporter.preprocess() hook runs after the configuration is resolved and before reporter.onBegin(), letting a reporter mark individual tests as skipped, excluded, fixed, or failing through a TestRun object:
class MyReporter { async preprocess({ config, suite, testRun }) { for (const test of suite.allTests()) { if (shouldSkip(test)) testRun.skip(test); } } }
Major versions
- 1.xsince 9 June 2021 · latest 1.64.1 · 128 releases
- 0.xsince 24 September 2020 · latest 0.1111.0 · 41 releases
Quality and security signals
What npm and deps.dev say about the latest release. Signals, not a verdict.
Reading npm and deps.dev…
Registry facts last checked 16 October 2026. Releases and advisories last read 16 October 2026.
Know when your own dependencies move
Inlinr tracks your coding time automatically. Switch dependency tracking on for a project and it reads that repository's manifest to show what is behind and what has been deprecated — off by default, one project at a time.