Skip to content
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

Allow specifying unpacked directory location #71

Open
hawkins opened this issue Jun 29, 2016 · 0 comments
Open

Allow specifying unpacked directory location #71

hawkins opened this issue Jun 29, 2016 · 0 comments

Comments

@hawkins
Copy link

hawkins commented Jun 29, 2016

I am packaging an application in Electron and using asar to do this. My application has a cfg folder that end users are allowed to edit to change core behavior of my application. I've specified all files in the cfg folder to remain unpacked, but this means users would navigate to resources/app.asar.unpacked/cfg instead of just cfg from the root level of the installation to make their changes.

It would be nice if there was a means by which to specify where unpacked files for asar are stored. Something like the following, maybe:

asar.createPackageWithOptions(appDir, buildDir, {"unpack": "*/cfg/*", "unpackedDirectory": "../"}, function () {
        ...
    });
@kevinsawicki kevinsawicki changed the title Allow specifying unpacked directory Allow specifying unpacked directory location Aug 18, 2016
@stale stale bot added the wontfix label Mar 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants