# playwright/release
Playwright v1.65.0
importance: criticalbreakingdeprecationmigrationfeature
Playwright’s test runner now supports Bun, and the release adds failure-focused reporting, exclusive test locks, and new APIs. It also changes TypeScript class-field behavior, actionability checks, cookie matching, proxy authentication, and several other behaviors that may require test or configuration updates.
affected
Playwright users may need to update test expectations, authentication and TypeScript configuration, and CI runtimes; teams can also opt into Bun and the new reporting features.
action
Review the breaking changes and update affected tests and configuration before upgrading; use Node.js 22, 24, or 26.
release_signals
-TypeScript class fields now follow `useDefineForClassFields`; initializers that read constructor parameter properties can fail. Move such initialization into the constructor or set `useDefineForClassFields` to `false`.
-Locator actions now wait for elements to be non-inert, so actions on persistently inert elements time out.
-Sharded runs with no matching tests now fail unless `--pass-with-no-tests` is used.
-Cookie matching now follows RFC 6265, and API request cookie serialization/storage behavior has changed.
-Proxy credentials now answer proxy challenges only; use `httpCredentials` to authenticate with websites.
-Accessible names and ARIA snapshots exclude text the browser does not render; API request `params` append to existing URL queries; CSS/Less/SCSS imports must exist; blob reports clear their output directory; CommonJS test locations now point to the start of the callee.
migration_steps5 steps
- 01For class-field initializers that access constructor parameter properties, move initialization into the constructor or set `"useDefineForClassFields": false` in `tsconfig.json`.
- 02Pass `--pass-with-no-tests` if a sharded run with no matching tests should succeed.
- 03Use `httpCredentials` for website authentication; proxy credentials now apply only to proxy challenges.
- 04Review tests relying on actions against inert elements, old cookie matching, accessible-name results, or replacement of existing URL query parameters.
- 05Use Node.js 22, 24, or 26 instead of Node.js 20.
code_snippet
bunx --bun playwright test# community_signal
How useful is this release to your stack?
—
net score
Sign in with GitHub to cast your vote.
Sign in with GitHub to vote
You’ll return to this release, then choose your vote.