This repository was archived by the owner on Feb 26, 2024. It is now read-only.
docs: expand on troubleshooting node-gyp errors #4013
Merged
Conversation
This file contains hidden or 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
davidmurdoch
suggested changes
Dec 14, 2022
legobeat
commented
Dec 14, 2022
davidmurdoch
approved these changes
Dec 14, 2022
node running as root is a common gotcha. While there are workarounds that make that work (`npm config set user 0`), it seems better to guide towards dropping privileges.
MicaiahReid
approved these changes
Dec 15, 2022
MicaiahReid
changed the title
|
Congrats, your important contribution to this open-source project has earned you a GitPOAP! GitPOAP: 2022 Ganache Contributor: Head to gitpoap.io & connect your GitHub account to mint! Learn more about GitPOAPs here. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
node running as root is a common gotcha.
While there are workarounds that make that work (
npm config set user 0), it seems better to guide towards dropping privileges.