Repository navigation
support for writing zip64 - #562
Merged
Merged
Conversation
Contributor
Author
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
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.
Summary
Add ZIP64 footer writing support for archives that exceed classic ZIP end-of-central-directory limits.
Previously, creating an archive with more than 65,535 entries fails while writing the classic EOCD record because entry counts are stored as UInt16 values. This change writes ZIP64 end records when needed and keeps the classic EOCD compatibility record with saturated placeholder values.
Changes
writeBigUInt64LEutility alongside the existing ZIP64 read helper.Test Plan
npm testResult:
93 passing