Playwright 1.65.0 was released on November 5, 2026, and 1.65.1 followed on November 13, 2026. The release notes list several changes that can break an existing suite, so read them before you bump the version.
What was announced
- The test runner can now run under Bun with the
--bunflag. Without the flag,bunx playwright teststill runs on Node.js. - A new
failuresreporter prints failures and successful retries as they happen, and the HTML, JSON and JUnit reporters get anonlyFailuresoption. - A built-in
-exclusive-test lock runs a test only when no other test is running. test.skip(),test.fixme(),test.fail()andtest.slow()now accept only a description.- Playwright no longer tests on Node.js 20. The release notes name Node.js 22, 24 or 26. Docker images now ship Node.js 26.
- 1.65.1 fixes two bugs: decorated classes with a static field failing to load when
useDefineForClassFieldsis false, and test locations being one column off under Bun 1.4.4 and later.
Why it matters for QA teams
Most of the risk is in the “Notable Changes” list, not the new features. These are the ones most likely to break a working suite:
- TypeScript class fields. They now follow
useDefineForClassFieldsfrom your tsconfig, the same as tsc. A page object that sets a field from a constructor parameter property, such asreadonly submit = this.page.getByRole(...), now throws a TypeError. Move the setup into the constructor or set the option to false. - Inert elements. Actions such as click, check, fill and selectOption now wait for the element to be not inert, and time out if it stays inert.
- Sharded runs. A run now fails with “No tests found” when no tests match across all shards. Pass
--pass-with-no-teststo allow it. - Cookies. Matching now follows RFC 6265, so
cookies()with a URL returns fewer host-only and path-prefix cookies than before. - Proxy credentials. They are no longer sent to websites. Use
httpCredentialsto authenticate on a site. - Accessible names and aria snapshots. Text the browser does not render, such as unslotted text or text directly inside a closed
details, is no longer included. This can changegetByRolewith a name andtoMatchAriaSnapshot()results. - API request params. String and URLSearchParams values are now appended to the URL query instead of replacing it.
- Stylesheet imports.
.css,.lessand.scssimports in test files load as empty modules, so the file must exist.
What we would do now
- Upgrade a branch first, not main. Run the full suite once and compare failures with your last green run.
- Search your page objects for fields that read a constructor parameter property. This is the change most likely to fail on day one.
- If you run Node.js 20 in CI, plan the move to 22 or later before you upgrade.
- Install 1.65.1, not 1.65.0, if you use decorators or Bun.
- If you use aria snapshots, re-run them and review any diffs by hand before you update the stored snapshots.
We have not run 1.65 against our own suites for this post. Everything above comes from the official release notes. For how Playwright compares with other runners, see our Selenium vs Playwright and Cypress vs Playwright guides, and our regression testing tools test, which ran Playwright 1.65.1.
Frequently Asked Questions
Is Playwright 1.65 a breaking release?
It includes several changes listed under “Notable Changes” that can break existing suites, mainly TypeScript class fields, inert elements and sharded runs with no tests. Most suites need small fixes, not rewrites.
Which version should I install, 1.65.0 or 1.65.1?
1.65.1. It is a bug-fix release for two regressions reported against 1.65.0.
Does Playwright 1.65 support Node.js 20?
Playwright no longer tests on Node.js 20. The release notes list Node.js 22, 24 and 26.
Sources
- Playwright release notes
- Playwright releases on GitHub (v1.65.0, v1.65.1)
One useful email a week
New guides, tool price changes and AI testing news. No spam.




