AIFix Issue 1121: Using exec does not terminate the command process #1
Conversation
This file contains 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.
AI-Generated Fix for Issue 1121 opened by laterdayi visible at shelljs#1121
State: open
Summary: The issue is that when using ShellJS's exec command, the command process is not terminated even if there is an error in the predev script, which should exit the terminal command process with a code of 1. The example provided shows that the predev script is executed before dev, and if there is an error in predev, the command process should be interrupted, but it is not. The user is using the latest version of Node and ShellJS on Windows.