-
-
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
Cannot get asar-unpack
to work
#390
Comments
Ah, figured it out. Using a globstar works, and no matter your directory structure, your files will be under "build": {
"asar-unpack": "**/app/external/*"
} |
It is the shame because we inherit this configuration option from the electron-packager. So, it is not smart and not user-friendly and no any checks :( So sad :( We will rework and introduce new smart option. |
Fixed – now we correctly set Also you can use extraResources . |
Please note |
Thank you @mikew for also sharing your answer. In 2018 this worked:
Successfully get this once the dmg is installed:
Now the tricky part is referring to it from within your app |
@challenger532 try changing: to "asarUnpack": ["node_modules/sqlite3"], |
|
Our Electron app uses
convert
from ImageMagick, and that needs some .xml files alongside the binary. Our electron folder ends up looking like this:I'm able to run
asar pack public/ public.asar --unpack 'public/external/*'
and get bothpublic.asar
andpublic.asar.unpacked
, but I cannot for the life of me figure out the path to be passed viabuild.asar-unpack
in the developmentpackage.json
.I've tried ...
... But am not able to get
app.asar.unpacked
. Is there anything I'm missing?The text was updated successfully, but these errors were encountered: