feat(child_process): support inline execFile callback options - #387
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ctate
marked this pull request as ready for review
September 23, 2026 05:10
This branch was successfully deployed
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.
Summary
execFile(file, args, { encoding: "utf8", maxBuffer: N }, callback)through the existing asynchronous child process runtime.maxBuffer. Other callback options retain explicit diagnostics.The native capture grows without enforcing
maxBuffer, consistent with the existing synchronous and promisified capture paths.Validation
main.pnpm node-compat:checkpass.pnpm test:ts7passes the full parity sweep (1,434 entries) after recording the new corpus fixture's baseline.pnpm test:sandbox: all 16 remote shards passed. Four local external lanes failed in the Vercel CLI network-jail preflight on Node 26.4.0: the unmodified CLI 56.2.0 first connects tosentry.ioinstead ofapi.vercel.com. The same isolated probe reachesapi.vercel.comfirst on Node 24.15.0. That suite and the sandbox harness are unchanged in this PR.