fix: use cross-spawn for Windows native runtime commands#137
Merged
Zhang-Henry merged 1 commit intoOpenLAIR:mainfrom Apr 9, 2026
Merged
fix: use cross-spawn for Windows native runtime commands#137Zhang-Henry merged 1 commit intoOpenLAIR:mainfrom
Zhang-Henry merged 1 commit intoOpenLAIR:mainfrom
Conversation
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
2 participants
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
Fix Windows
spawn EINVALerrors when preparing native runtime commands in development workflows.Cause
On Windows, launching
.cmdwrappers such asnpm.cmdandnpx.cmdthroughchild_process.spawn(..., { shell: false })can fail withspawn EINVAL.Changes
cross-spawninscripts/native-runtime.mjscross-spawninelectron/cli.mjsVerification
node scripts/native-runtime.mjs nodeNotes
This is a small Windows compatibility fix and does not change behavior on non-Windows platforms.