This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade playwright from 1.33.0 to 1.38.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
- The recommended version is **253 versions** ahead of your current version.
- The recommended version was released **a month ago**, on 2023-09-21.
Release notes Package name: playwright
#27071 - expect(value).toMatchSnapshot() deprecation announcement on V1.38 #27072 - [BUG] PWT trace viewer fails to load trace and throws TypeError #27073 - [BUG] RangeError: Invalid time value #27087 - [REGRESSION]: npx playwright test --list prints all tests twice #27113 - [REGRESSION]: No longer able to extend PlaywrightTest.Matchers type for locators and pages #27144 - [BUG]can not display trace #27163 - [REGRESSION] Single Quote Wrongly Escaped by Locator When Using Unicode Flag #27181 - [BUG] evaluate serializing fails at 1.38
Browser Versions
Chromium 117.0.5938.62
Mozilla Firefox 117.0
WebKit 17.0
This version was also tested against the following stable channels:
Breaking Changes: Playwright no longer downloads browsers automatically
Note
If you are using @ playwright/test package, this change does not affect you.
Playwright recommends to use @ playwright/test package and download browsers via npx playwright install command. If you are following this recommendation, nothing has changed for you.
However, up to v1.38, installing the playwright package instead of @ playwright/test did automatically download browsers. This is no longer the case, and we recommend to explicitly download browsers via npx playwright install command.
v1.37 and earlier
playwright package was downloading browsers during npm install, while @ playwright/test was not.
v1.38 and later
playwright and @ playwright/test packages do not download browsers during npm install.
Recommended migration
Run npx playwright install to download browsers after npm install. For example, in your CI configuration:
- run: npm ci
- run: npx playwright install --with-deps
Alternative migration option - not recommended
Add @ playwright/browser-chromium, @ playwright/browser-firefox and @ playwright/browser-webkit as a dependency. These packages download respective browsers during npm install. Make sure you keep the version of all playwright packages in sync:
#23622 - [Docs] Provide a description how to correctly use expect.configure with poll parameter #23666 - [BUG] Live Trace does not work with Codespaces #23693 - [BUG] attachment steps are not hidden inside expect.toHaveScreenshot()
Browser Versions
Chromium 115.0.5790.13
Mozilla Firefox 113.0
WebKit 16.4
This version was also tested against the following stable channels:
New uninstall CLI command to uninstall browser binaries:
$ npx playwright uninstall # remove browsers installed by this installation
$ npx playwright uninstall --all # remove all ever-install Playwright browsers
Both UI mode and trace viewer now could be opened in a browser tab:
$ npx playwright test --ui-port 0 # open UI mode in a tab on a random port
$ npx playwright show-trace --port 0 # open trace viewer in tab on a random port
β οΈ Breaking changes
playwright-core binary got renamed from playwright to playwright-core. So if you use playwright-core CLI, make sure to update the name:
$ npx playwright-core install # the new way to install browsers when using playwright-core
This change does not affect @ playwright/test and playwright package users.
Browser Versions
Chromium 115.0.5790.13
Mozilla Firefox 113.0
WebKit 16.4
This version was also tested against the following stable channels:
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade playwright from 1.33.0 to 1.38.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.- The recommended version is **253 versions** ahead of your current version. - The recommended version was released **a month ago**, on 2023-09-21.
Release notes
Package name: playwright
Highlights
#27071 - expect(value).toMatchSnapshot() deprecation announcement on V1.38
#27072 - [BUG] PWT trace viewer fails to load trace and throws TypeError
#27073 - [BUG] RangeError: Invalid time value
#27087 - [REGRESSION]: npx playwright test --list prints all tests twice
#27113 - [REGRESSION]: No longer able to extend PlaywrightTest.Matchers type for locators and pages
#27144 - [BUG]can not display trace
#27163 - [REGRESSION] Single Quote Wrongly Escaped by Locator When Using Unicode Flag
#27181 - [BUG] evaluate serializing fails at 1.38
Browser Versions
This version was also tested against the following stable channels:
UI Mode Updates
New APIs
browserContext.on('weberror')
locator.pressSequentially()
reporter.onEnd()
now reportsstartTime
and total runduration
.Deprecations
page.type()
,frame.type()
,locator.type()
andelementHandle.type()
.Please use
locator.fill()
instead which is much faster. Uselocator.pressSequentially()
only if there is aspecial keyboard handling on the page, and you need to press keys one-by-one.
Breaking Changes: Playwright no longer downloads browsers automatically
Note
If you are using
@ playwright/test
package, this change does not affect you.Playwright recommends to use
@ playwright/test
package and download browsers vianpx playwright install
command. If you are following this recommendation, nothing has changed for you.However, up to v1.38, installing the
playwright
package instead of@ playwright/test
did automatically download browsers. This is no longer the case, and we recommend to explicitly download browsers vianpx playwright install
command.v1.37 and earlier
playwright
package was downloading browsers duringnpm install
, while@ playwright/test
was not.v1.38 and later
playwright
and@ playwright/test
packages do not download browsers duringnpm install
.Recommended migration
Run
npx playwright install
to download browsers afternpm install
. For example, in your CI configuration:Alternative migration option - not recommended
Add
@ playwright/browser-chromium
,@ playwright/browser-firefox
and@ playwright/browser-webkit
as a dependency. These packages download respective browsers duringnpm install
. Make sure you keep the version of all playwright packages in sync:Browser Versions
This version was also tested against the following stable channels:
Highlights
#26496 - [REGRESSION] webServer stdout is always getting printed
#26492 - [REGRESSION] test.only with project dependency is not working
Browser Versions
This version was also tested against the following stable channels:
Watch the overview: Playwright 1.36 & 1.37
β¨ New tool to merge reports
If you run tests on multiple shards, you can now merge all reports in a single HTML report (or any other report)
using the new
merge-reports
CLI tool.Using
merge-reports
tool requires the following steps:Adding a new "blob" reporter to the config when running on CI:
The "blob" reporter will produce ".zip" files that contain all the information
about the test run.
Copying all "blob" reports in a single shared location and running
npx playwright merge-reports
:Read more in our documentation.
π Debian 12 Bookworm Support
Playwright now supports Debian 12 Bookworm on both x86_64 and arm64 for Chromium, Firefox and WebKit.
Let us know if you encounter any issues!
Linux support looks like this:
π UI Mode Updates
Browser Versions
This version was also tested against the following stable channels:
#24316 - [REGRESSION] Character classes are not working in globs in 1.36
Browser Versions
This version was also tested against the following stable channels:
#24184 - [REGRESSION]: Snapshot name contains some random string after test name when tests are run in container
Browser Versions
This version was also tested against the following stable channels:
Watch the overview: Playwright 1.36 & 1.37
Highlights
ποΈ Summer maintenance release.
Browser Versions
This version was also tested against the following stable channels:
#23622 - [Docs] Provide a description how to correctly use expect.configure with poll parameter
#23666 - [BUG] Live Trace does not work with Codespaces
#23693 - [BUG] attachment steps are not hidden inside expect.toHaveScreenshot()
Browser Versions
This version was also tested against the following stable channels:
Playwright v1.35 updates
Highlights
UI mode is now available in VSCode Playwright extension via a new "Show trace viewer" button:
UI mode and trace viewer mark network requests handled with
page.route()
andbrowserContext.route()
handlers, as well as those issued via the API testing:New option
maskColor
for methodspage.screenshot()
,locator.screenshot()
,expect(page).toHaveScreenshot()
andexpect(locator).toHaveScreenshot()
to change default masking color:New
uninstall
CLI command to uninstall browser binaries:Both UI mode and trace viewer now could be opened in a browser tab:
playwright-core
binary got renamed fromplaywright
toplaywright-core
. So if you useplaywright-core
CLI, make sure to update the name:$ npx playwright-core install # the new way to install browsers when using playwright-core
This change does not affect
@ playwright/test
andplaywright
package users.Browser Versions
This version was also tested against the following stable channels:
Commit messages
Package name: playwright
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
π§ View latest project report
π Adjust upgrade PR settings
π Ignore this dependency or unsubscribe from future upgrade PRs