-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
disable "unpack execuatable" #879
Comments
No. In general, it is ok — doesn't affect performance. Does it lead to runtime error? |
no, just lead to uncomfortable |
If it doesn't lead to any runtime error and conditional statements in the code, then I am going to close won't fix. Don't you mind? |
Log level changed from info to debug. |
develar
added a commit
that referenced
this issue
Nov 5, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a module contains executable binary files, but they never execute them directly, only copy them to outside directory via
fs
. It works in asar packages.Is there any way to say don't unpack these module, just put them into asar package?
The text was updated successfully, but these errors were encountered: