This repository has been archived by the owner on Oct 7, 2020. It is now read-only.
Adding "|| exit 0" to prevent downstream failure in npm processes #166
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
Various environmental or project scenarios may lead to a failure when calling lightercollective from postinstall. This is not known to be a lightercollective failure, but instead of a failure to properly call the lightercollective library. One such known scenario on Windows being multiple path casings being passed to child_process.spawn when npm-lifecycle processes postinstall. Discussion on lifecycle/postinstall Win32 issue here: npm/npm-lifecycle#29 This PR is intended to address this discussion: WebReflection#165
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Various environmental or project scenarios may lead to a failure when calling lightercollective from postinstall. This is not known to be a lightercollective failure, but instead of a failure to properly call the lightercollective library. One such known scenario on Windows being multiple path casings being passed to child_process.spawn when npm-lifecycle processes postinstall.
Discussion on lifecycle/postinstall Win32 issue here: npm/npm-lifecycle#29
This PR is intended to address this discussion: #165