Skip to content

Conversation

@DougReeder
Copy link
Member

In both the old and new code, errors thrown by execSync are caught and the process exited. The new code just brings the comparisons and logging inside the try-catch. In the unlikely event that they threw an error, that would almost certainly be a coding error, in which case the process should exit. However, that code is so simple that practically speaking, the new and old code are equivalent. I believe this way is more idiomatic.

Supersedes hrithikwins/ce-npm#5

Copy link
Member

@Exairnous Exairnous left a comment

Choose a reason for hiding this comment

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

LGTM. Thank you. Merging.

@Exairnous Exairnous merged commit b48d696 into Hubs-Foundation:master Sep 24, 2024
@DougReeder DougReeder deleted the npm-err-msg branch September 30, 2024 02:32
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.

2 participants