Fix jbrowse create/jbrowse upgrade CLI intermittent failures #3686
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.
Some people are reporting corrupt files from node-unzipper both to our project and in issues on their repo e.g. ZJONSSON/node-unzipper#271
In the absence of this getting fixed upstream, this PR proposes using an alternative library, yauzl (yet another un-zip library) with a front end provided by npm package 'decompress' (see https://github.com/kevva/decompress-unzip/blob/master/package.json#L31) since yauzl is a bit tricky to use by itself
The firebase project maybe ran into same issue and created their own unzipper based on native nodejs zlib which seemed nice but it's not published on npm and I couldn't get it to work firebase/firebase-tools#5714