-
Notifications
You must be signed in to change notification settings - Fork 5
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
Bad argument at ChildProcess.spawn #449
Comments
hmm difficult to tell what is happening with no code to reproduce the issue. what version of the |
I think 1.4.12 but I'd need to check to be sure... I'll also try and get some sample code posted here so you can see, but basically the |
are you calling |
Correct... Calling it from an Electron app. |
this module is expected to be used inside a node.js app (node process), so i'm afraid that calling it from a electron app will not work right now. |
Having the same issue.
|
@rcrodrigues i'm not sure about your issue, do you have a test case where this error happens? just keep in mind that this package is not going to work if you are using it in an electron application, this package works when you use it from a node.js app |
Same issue. |
Got this working great on the Mac and then ported over to RPi to have it throw this error. After some digging find out that the Mac was running electron-html-to@2.2.0 and the RPi was running electron-html-to@2.3.0. After some additional digging find out that the call to get the Electron path is failing... the electron var actually has the entire electron object... not the Electron path.
And this issue is apparently also in electron-workers@1.10.0
electron = getElectronPathFromPackage('electron');
... actually returns the full Electron object and not the file path to the binary as indicated here: https://github.com/electron-userland/electron-prebuilt
Is something misconfigured or is there a simple workaround that I'm missing?
The text was updated successfully, but these errors were encountered: