[adimoldovan]

Updates @playwright/test from 1.61.1 to 1.64.1. Only package.json and package-lock.json change.

Playwright 1.63 added test locks, and 1.64 added test.describe.configure( { lock } ). A follow-up change uses them to run more of the E2E suite in parallel.

The lockfile changes only the @playwright/test, playwright and playwright-core entries. Playwright now requires Node 20 or later. This repository already requires Node 24.

Testing

To test:

1. npm ci
2. npm exec --no -- playwright install chromium
3. npm run env:start && npm run env:install
4. npm run test:e2e

Trac ticket: https://core.trac.wordpress.org/ticket/65857

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Version bump, test runs and this description. I reviewed the result.

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props adrianmoldovanwp, lancewillett.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[lancewillett]

This overlaps with #12861, which is open on the same ticket and bumps @playwright/test from 1.61.1 to 1.62.1. Whichever lands second will conflict. If #12861 lands second as-is, it moves Playwright back to 1.62.1, which is older than the 1.63 that test locks need. Its Playwright bump should either be dropped or changed to 1.64.1.

_{AI review · claude-opus-5-5}

[Copilot]

🔵 Needs a closer look

Package artifact integrity and compatibility with the existing E2E suite still need CI or human confirmation.

No open issues 🎉

What changed in this PR

Updates Playwright from 1.61.1 to 1.64.1, preparing the E2E test tooling for a follow-up change that uses test locks to increase parallel execution.

Changes:

• Bumps @playwright/test and its locked playwright and playwright-core dependencies to 1.64.1.
• Updates Playwright’s Node requirement to 20+, compatible with the repository’s stated Node 24 requirement.
• Removes Playwright’s optional fsevents dependency declaration.

File	Description
package.json	Pins @playwright/test to 1.64.1.
package-lock.json	Updates Playwright versions, artifact metadata, engine requirements, and optional dependency metadata.

_{Review effort: Balanced}

[lancewillett]

PR #14896 landed in https://core.trac.wordpress.org/changeset/64740