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

fix: do not ignore errors when checking npm/yarn output #1147

Merged
merged 2 commits into from
Oct 10, 2023

Conversation

josegonzalez
Copy link
Contributor

Dropping stderr/stdout on the floor results in mysterious buildpack failures in certain cases. For instance, if there is a .yarnrc.yml that requires an environment variable, yarn --version will output an error, but then the existing code would just silence that, causing users to think that the yarn install failed with no real recourse.

Dropping stderr/stdout on the floor results in mysterious buildpack failures in certain cases. For instance, if there is a `.yarnrc.yml` that requires an environment variable, `yarn --version` will output an error, but then the existing code would just silence that, causing users to think that the yarn install failed with no real recourse.
Copy link
Member

@joshwlewis joshwlewis left a comment

Choose a reason for hiding this comment

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

Looks good, just needs a changelog entry.

@josegonzalez
Copy link
Contributor Author

Added the changelog entry.

@colincasey colincasey self-requested a review October 10, 2023 15:24
@colincasey colincasey merged commit bb9fed9 into heroku:main Oct 10, 2023
11 of 12 checks passed
@colincasey colincasey mentioned this pull request Oct 11, 2023
@josegonzalez josegonzalez deleted the patch-1 branch October 14, 2023 02:28
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.

3 participants