Repository navigation
Conversation
🤖 PR meta 🤖🏷️ LabelsThis pull request needs exactly one label indicating its type, and has 0.
Read more about Type labels in Gutenberg. If you cannot add labels yourself, a reviewer can do it for you. 📦 Bundle sizeSize Change: 0 B Total Size: 8.22 MB
⚡ PerformanceShow the resultsClient side metrics exclude the server response time. front-end-block-theme
front-end-classic-theme
media-processing
media-upload
post-editor
site-editor
|
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
b075865
into
codex/vitest-internal-lint-baseline
* E2E Tests: Remove unused Jest peer dependency * E2E Tests: Link Jest peer cleanup changelog
…ndencies (#83502) * Tests: Switch internal linting to the Vitest baseline * Tests: Simplify internal lint verification * E2E Tests: Remove unused Jest peer dependency (#83505) * E2E Tests: Remove unused Jest peer dependency * E2E Tests: Link Jest peer cleanup changelog * Tests: Address Vitest lint migration feedback --- Co-authored-by: ciampo <mciampini@git.wordpress.org> Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org>
…ndencies (WordPress#83502) * Tests: Switch internal linting to the Vitest baseline * Tests: Simplify internal lint verification * E2E Tests: Remove unused Jest peer dependency (WordPress#83505) * E2E Tests: Remove unused Jest peer dependency * E2E Tests: Link Jest peer cleanup changelog * Tests: Address Vitest lint migration feedback --- Co-authored-by: ciampo <mciampini@git.wordpress.org> Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org>
Stacked on #83502. See #83089, step 1 dependency cleanup.
What?
Remove the unused Jest peer dependency from
@wordpress/e2e-tests.Why?
The package contains fixtures for Playwright tests, but installing it still pulls in Jest. Neither its current source nor the published
9.21.0fixtures use Jest.How?
Remove the peer from the package manifest, lockfile and retained-Jest inventory. Add a package changelog entry. Fixture files stay unchanged.
Testing Instructions
Pack the candidate with workspace dependencies converted to published versions, then install it in an empty npm project. Confirm that Jest is absent and the
plugins,mu-pluginsandassetsdirectories are present. Installing released@wordpress/e2e-tests@9.21.0in an empty project provides the comparison: it automatically installs Jest.Local verification
The released package installed Jest 30.5.2; the packed candidate installed without Jest. All 317 fixture files matched the published package byte for byte. The candidate consumer audit reported no vulnerabilities.
Build, JavaScript lint, package metadata, lockfile, dependency alignment, published dependency, test routing and convention checks passed. The repository audit reported 45 existing advisories; this change leaves its resolved dependency graph unchanged.
Use of AI Tools
Codex implemented the removal and ran the package and repository checks.