add optional dependency bindings due to npm warning #5348
Merged
Conversation
This file contains 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
- Unexpected warning for https://registry.npmjs.org/: Miscellaneous - Warning EAI_AGAIN: request to https://registry.npmjs.org/bindings failed, - reason: getaddrinfo EAI_AGAIN registry.npmjs.org - Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
|
After days, I constantly get this diff when switching branches. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Today if I run
npm installonmasterbranch it modifiespackage-lock.jsonwith the following warning:Warning EAI_AGAIN: request to https://registry.npmjs.org/bindings failed,
reason: getaddrinfo EAI_AGAIN registry.npmjs.org
The changes are committed in this PR
@alexcjohnson @antoinerg do you get an identical diff?
@plotly/plotly_js