Bump Playwright to 1.49.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@playwright/test (source)	1.48.2 -> 1.49.0
playwright (source)	^1.48.2 -> ^1.49.0
playwright (source)	1.48.2 -> 1.49.0

---

Release Notes

microsoft/playwright (@​playwright/test)

v1.49.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "on sunday before 6:00am" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[mui-bot]

Netlify deploy preview

https://deploy-preview-44527--material-ui.netlify.app/

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 92bdddd

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[aarongarciah]

@mui/code-infra Renovate didn't update the Docker image version in .circleci/config.yml as it did in previous Playwright bumps https://github.com/mui/material-ui/pull/44222/files#diff-78a8a19706dbd2a4425dd72bdab0502ed7a2cef16365ab7030a5a0588927bf47R383

[JCQuintas]

@mui/code-infra Renovate didn't update the Docker image version in .circleci/config.yml as it did in previous Playwright bumps https://github.com/mui/material-ui/pull/44222/files#diff-78a8a19706dbd2a4425dd72bdab0502ed7a2cef16365ab7030a5a0588927bf47R383

It can't update images because new versions don't use ubuntu focal anymore. Gotta move them to noble

[aarongarciah]

After manually pointing Playwright Docker images to playwright:v1.49.0-noble, the test_regression check fails: ReferenceError: __dirname is not defined

https://app.circleci.com/pipelines/github/mui/material-ui/143497/workflows/ca1efb19-79a9-4523-9b6a-9010a8de2c37/jobs/772782

[michaldudak]

We had the same issue in Base UI. For some reason, the main test file has to be proper CommonJS or ESM, not a blend of both (which is actually a good thing).

See https://github.com/mui/base-ui/pull/836/files#diff-a00cb0d81882c4a00f2935b720a1e611c08e123551be2103da06c7022cd35ae7

[aarongarciah]

Thanks @michaldudak. It now works after applying that change.

@mui/code-infra this is ready for review. There's a lot of changed screenshots in Argos (946), most of them probably caused by the Chromium version update (129 -> 131) causing minor differences in text rendering.

[JCQuintas]

We had the same issue in Base UI. For some reason, the main test file has to be proper CommonJS or ESM, not a blend of both (which is actually a good thing).

See https://github.com/mui/base-ui/pull/836/files#diff-a00cb0d81882c4a00f2935b720a1e611c08e123551be2103da06c7022cd35ae7

This is odd, we didn't have this issue. mui/mui-x#15493

[JCQuintas]

Thanks @michaldudak. It now works after applying that change.

@mui/code-infra this is ready for review. There's a lot of changed screenshots in Argos (946), most of them probably caused by the Chromium version update (129 -> 131) causing minor differences in text rendering.

Our argos changed a lot as well

[JCQuintas]

I believe the issue is that you are using @mui/internal-test-utils/setupBabelPlaywright inside test/regressions/.mocharc.js instead of @mui/internal-test-utils/setupBabel

[JCQuintas]

The playwright specific config seems unnecessary to me btw, maybe we should remove it @michaldudak

[michaldudak]

Changing this to setupBabel causes the tests in Base UI to explode, so it may require a bit more work. I'd love to get rid of webpack and mocha and replace them with vite and vitest at some point.

[JCQuintas]

Ah, but this seems to work in core. I'm still having trouble with vitest on X, but the next step would be to try to use the same tools everywhere indeed.