Repository navigation
feat!: upgrade execa to v10 and require Node 22 - #601
Merged
Merged
Conversation
execa 10 removes execaCommand(); the shell branch now uses the
tagged-template form execa(options)`${command}`. The non-shell branch
is unchanged — it already used the local parseCommandString helper that
execa's migration guide recommends.
execa 10 also raises its engine floor to Node 22. packages/run declared
a non-standard top-level "node": ">=16" field, which npm never enforced;
it is replaced with a real engines.node ">=22" so the requirement is
actually surfaced at install time.
Verified: 268 repo tests pass, plus end-to-end runs of examples/run and
the search CLI exercising both the shell and non-shell code paths.
Error shapes (shortMessage, exitCode, ENOENT handling) are unchanged
from execa 9.
BREAKING CHANGE: @node-cli/run now requires Node.js 22 or later.
This was referenced Jul 21, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrades
execain@node-cli/runfrom9.6.1to10.0.0.Breaking changes in execa 10 that touch this package
run?execaCommand()/execaCommandSync()removedengines.node^18.19.0 || >=20.5.0→>=22ChildProcess(.on(),.send()move to.nodeChildProcess)stdio: [..., 'ipc']→ipc: trueinput/inputFilenow take precedence over inherited stdinThe code change
The non-shell branch is untouched — it already used the local
parseCommandStringhelper that execa's migration guide points to.The Node floor
packages/run/package.jsondeclared a non-standard top-level"node": ">=16"field. npm and pnpm readengines.node, so that floor was never enforced. It is replaced with a real"engines": { "node": ">=22" }so execa 10's requirement is surfaced at install time rather than being silently transitive.Node 20 reached EOL on 2026-04-30, so a Node 22 floor excludes only unsupported runtimes. CI already runs 24.x.
No downstream pin bumps needed —
search,npmrc, andexamples/runconsumerunviaworkspace:*.Verification
pnpm test— 268 tests across 12 packages passpnpm lintclean across 13 projects;tsc+ swc build cleanexamples/run/run-example.jsoutput is byte-identical to execa 9, and the builtsearchCLI exercised bothruncode paths (id -nunon-shell,--command "wc -l"shell)shortMessage,exitCode, and ENOENT handling match execa 9 for every existing assertionFollow-up (not in this PR)
The other 13 packages carry the same typo'd, non-enforced
"node"field. Nothing reads it, butsearchandnpmrcnow transitively require Node 22 while declaring>=18/>=16. Worth a separate cleanup.🤖 Generated with Claude Code
https://claude.ai/code/session_01WxPdHpfW5B4evcecAmHHqa