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

Asar is applied on current folder instead of project directory #1459

Closed
taffeldt opened this issue Apr 11, 2017 · 1 comment
Closed

Asar is applied on current folder instead of project directory #1459

taffeldt opened this issue Apr 11, 2017 · 1 comment

Comments

@taffeldt
Copy link

taffeldt commented Apr 11, 2017

  • Version: 16.8.2

No version of electron-updater is being used.

  • Target: Windows x64 (probably happend with any)

I am using a setup with two package.json files.
My build process compiles my Typescript files into Javascript and stores them in the dist/ folder. Inside this dist folder is the inner package.json containing the electron builder configuration inside the build tag.
This build tag contains: "build: { "appId": "com.example.project", "asar": false }

The outer package.json calls the builder via a NPM command: build --dir --projectDir dist

The result is just as expected and works absolutely fine. If I set asar to true, though, the command crashes telling me the index.js could not be found. Calling the command via console directly does the same thing if I call it from the main folder. Calling it from the subfolder dist instead without setting the --projectDir flag works fine.

Executing asar list on the broken .asar file shows all of my files from the main directory instead of the subfolder's entries.

@develar
Copy link
Member

develar commented Feb 1, 2018

I hope it is obsolete now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants