fix: Incorporate electron/asar per-file unpack flag to bypass pattern is too long minimatch limitation [DO NOT MERGE]
#120
+97
−48
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
…rateOrderingConfig` and unit test for generating an ordering file that contains explicit unpack flag per file
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.
[DO NOT MERGE]
Depends on electron/asar#350
Resolves: #117
Notes:
generateOrderingConfigand unit test for generating an ordering file that contains an explicit unpack flag per fileOpen Question
asar.listPackagerespect/retain the asar ordering in its output? Or do I need to manually parse the Asar Header for ordering?