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
Support running inside asar packaged app #251
Comments
I have no idea. I don't know asar. Line 123 in 5e2c65c
You could set the Line 116 in 5e2c65c
See: https://github.com/giggio/node-chromedriver#force-download Are you able to do that? |
I ended up not using asar at all. node-chromedriver/bin/chromedriver Line 3 in 5e2c65c
Btw, in my use case, i am shipping an app that uses the chrome driver, so I need to handle cases where users have different chrome versions, and where they update chrome once in a while. |
Spawning the process is core to what this package does. If you run it, that's what it'll do. If you want to run it, how to do it without spawn? Regarding the multiple versions, can you elaborate? What do you need? |
I'm closing it as I am not sure where this is going. Feel free to elaborate on a new issue. |
I am using node-chromedriver as part of an application that is distributed to customers.
I am building the app with electron-builder, but get the following error on startup:
I somehow narrowed down the issue to being related to asar packaging.
When packaging the app into an asar archive, the chromedriver will throw an error, but it will work as expected if not packaging as asar.
See the following links that discuss the issue:
https://www.electronjs.org/docs/tutorial/application-packaging
And here:
electron/electron#9459
Do you think that it would be possible to make chromedriver work from within an asar archive?
The text was updated successfully, but these errors were encountered: