fix: resolve spawn EINVAL on Windows by enabling shell execution#2
Open
farsh1024 wants to merge 1 commit into
Open
fix: resolve spawn EINVAL on Windows by enabling shell execution#2farsh1024 wants to merge 1 commit into
farsh1024 wants to merge 1 commit into
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
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.
Fix Windows spawn EINVAL error by enabling shell execution
Problem:
When running the Web UI on Windows, the backend fails to execute the CLI command using child_process.spawn, resulting in the error “spawn EINVAL”. This prevents the deobfuscation process from running and no output files are generated.
Cause:
On Windows, .cmd files such as npm.cmd must be executed within a shell environment. Calling spawn without enabling shell execution causes the process to fail with an EINVAL error.
Solution:
Add “shell: true” to the spawn options in the runDeobfuscate function so that npm.cmd is executed correctly on Windows.
Impact:
This fix restores Web UI functionality on Windows systems. It does not affect behavior on Linux or macOS and maintains backward compatibility.
Test:
Verified that CLI usage works as expected. Verified that the Web UI can successfully execute deobfuscation and generate output files on Windows after applying the fix.