Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Return error ENOENT when program not found on Windows #470

Closed
wants to merge 1 commit into from

Conversation

lynxtaa
Copy link

@lynxtaa lynxtaa commented Jun 10, 2021

@ehmicky ehmicky self-requested a review June 11, 2021 21:24
Copy link
Collaborator

@ehmicky ehmicky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for trying to fix this issue @lynxtaa!

However, this PR would revert #447, which was fixing the problem described in #446.

Several users (including me) have actually suggested removing the ENOENT logic from node-cross-spawn because it is unreliable in too many cases, so using it in execa is probably not a good idea unfortunately (see my comment in #469 (comment)).

@lynxtaa lynxtaa closed this Jun 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Subprocess should emit error if executable path doesn't exist in Windows
2 participants