Improve Compression from Generator without CompressionStreams #60
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
✅ Deploy Preview for emulatorjs-org ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Contributor
Author
|
Actually, it's too much slower for my liking (and I don't have time to add a fallback between this and the faster |
Member
|
If you wanted, an option whether or not to compress the file could have the same result :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This aims to accomplish the same compression improvements as #59 , but this time without Compression or Decompression Streams.
JSZip is quite a bit slower than the browser-native CompressionStreams, so drafting until I can add a progress bar for it...