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

Use non-zero exit codes to determine child process failures #1022

Merged

Conversation

steveukx
Copy link
Contributor

@steveukx steveukx commented Nov 9, 2021

When running node through some IDE debugging tools, stderr will always have content relating to the debugger connecting.

This PR therefore adds a check that the exitCode for the yarnpkg child process is non-zero when checking for a failed attempt to read yarn workspace details rather than simply the presence of content on stderr.

Closes #1021 1021

…ays have content relating to the debugger connecting.

This PR therefore adds a check that the `exitCode` for the `yarnpkg` child process is non-zero when checking for a failed attempt to read yarn workspace details rather than simply the presence of content on `stderr`.
@changeset-bot
Copy link

changeset-bot bot commented Nov 9, 2021

🦋 Changeset detected

Latest commit: b188951

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
modular-scripts Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@LukeSheard LukeSheard merged commit d670354 into jpmorganchase:main Nov 10, 2021
This was referenced Nov 10, 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.

Yarn workspace info fails to load when run with IDE debugging
2 participants