Skip to content

Build/Test Tools: Remove npx commands in the 6.8 branch - #13109

Open
adimoldovan wants to merge 2 commits into
WordPress:6.8from
adimoldovan:65864-remove-npx-6.8
Open

Build/Test Tools: Remove npx commands in the 6.8 branch#13109
adimoldovan wants to merge 2 commits into
WordPress:6.8from
adimoldovan:65864-remove-npx-6.8

Conversation

@adimoldovan

@adimoldovan adimoldovan commented Aug 17, 2026

Copy link
Copy Markdown

Backport of r63309, already in trunk via #13021, to the 6.8 branch. It replaces the two remaining npx calls in Gruntfile.js with npm exec --no, which fails on a missing package instead of installing it.

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

Testing instructions

  1. Run npm ci.
  2. Run npm ls update-browserslist-db. It is now a direct devDependency at 1.1.1, and the copy under browserslist is deduped, so the tree gains no package.
  3. Run npm exec --no -- update-browserslist-db --version. It prints browserslist-lint 1.1.1 and downloads nothing.
  4. Move node_modules/update-browserslist-db aside and run npm exec --no -- update-browserslist-db again. It fails with npx canceled due to missing packages and no YES option instead of fetching the package. Move the directory back.
  5. Run npm exec --no -- wp-scripts --help. It runs the installed binary and prints Script name is missing.

Use of AI Tools

AI assistance: Yes — Claude Code (Claude Opus 5) applied r63309 to the 6.8 branch and verified the changeset.

`npx` installs a missing package and runs its install scripts. This replaces
both `npx` calls in `Gruntfile.js` with `npm exec --no`, which runs only an
installed binary and fails when the package is missing.
`update-browserslist-db` becomes a direct `devDependency`.

Backport of r63309.
@desrosj desrosj moved this from Backlog to In progress in WordPress Project Build Tooling Aug 17, 2026
@adimoldovan adimoldovan changed the title Build/Test Tools: Remove all npx commands Build/Test Tools: Remove npx commands in the 6.8 branch Aug 18, 2026
@github-actions

Copy link
Copy Markdown

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.

@adimoldovan
adimoldovan marked this pull request as ready for review August 18, 2026 09:23
@github-actions

Copy link
Copy Markdown

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 props-bot label.

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

Props adrianmoldovanwp.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In progress

Development

Successfully merging this pull request may close these issues.

2 participants