-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to pick one asar, instead of keeping both #2
Comments
Actually... Adding an option is not really necessary. Just make the 'auto' option the default behaviour and it will automatically work in both cases. |
@NielsLeenheer are the SHAs of your asar files the same? If so then yeah, adding that kind of optimization makes sense to me |
Yes, the SHAs are identical. |
Fixed in 82acb6f |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to have an option which you can use to configure what to do with the two asar files. Currently the default behaviour is to keep them both and use a runtime check to determine which to run.
The asar of our app quite big, about 30 MB and the arm64 and x64 versions are identical. In our case the default behaviour would add an unneeded 30 MB to our .app.
Perhaps four options:
x64, arm64, both and auto.
With auto doing a check to see if the two asar's are identical. If identical, pick one. And if different, keep both.
The text was updated successfully, but these errors were encountered: