[nucliweb]

Summary

• Playwright 1.65.1 in the lockfile, from 1.63.0. It brings Chromium 159.
• Copy prompt. PLAYWRIGHT in lib/snippet-prompt.mjs goes from 1.63 to 1.65: the prompt of a snippet page installs and runs the version the CLI is tested with. The tests that spell the version change with it.
• Back-Forward-Cache tests. Chromium 159 does not register an unload handler unless the page sends Permissions-Policy: unload=(self), and a frame also needs allow="unload" from the page that embeds it. window.onunload = fn leaves window.onunload at null, and notRestoredReasons gives only masked. The pages of cli/tests/e2e/bfcache.test.js that test an unload handler send the header, and the frame is allowed.
• CHANGELOG: an entry under ## [Unreleased].

The snippet does not change. Without a registered handler nothing blocks the bfcache, so there is nothing to report.

Test plan

On macOS with Node 26.13.1 and Playwright 1.65.1:

• npm test
• npm run build and npm run check:built-snippets (59 snippets); the generated public/CoreWebVitals/LCP.md has playwright@1.65
• npm run test:extension:e2e: 93 of 93
• npm run test:e2e --prefix cli: 795 of 795
• cli/tests/e2e/bfcache.test.js on its own, 3 times: 6 of 6. Without the change to the fixture, 2 of its 6 tests fail the 3 times
• A script with CDP, outside the repository: with the header and allow="unload", Page.backForwardCacheNotUsed gives UnloadHandlerExistsInMainFrame and UnloadHandlerExistsInSubFrame, and notRestoredReasons gives unload-listener for the page and for the frame
• npm run lint and npm run check:emoji
• CI, and the evals of the prompt, which run because the prompt changes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
webperf-snippets	Ready	Preview	Nov 14, 2026 2:19pm UTC