We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After building for windows, the module gives me this error, no idea what causes this.
I'm using latest version from GitHub. Works fine when running in node itself.
The text was updated successfully, but these errors were encountered:
I fixed this, by using child_process.execFile instead of spawn
child_process.execFile
spawn
Sorry, something went wrong.
Could you try again with the new version 0.3.0? It uses execa under the hood to execute the file.
0.3.0
execa
If it doesn't fix it we should probably file a bug there...
It still exists in version 0.3.0. and I don't want to spawn new process or grab the child process.
Having the same error even without building (just by running npm start): Windows 10 (Virtual Machine) v4.0.1
npm start
No branches or pull requests
After building for windows, the module gives me this error, no idea what causes this.
I'm using latest version from GitHub.
Works fine when running in node itself.
The text was updated successfully, but these errors were encountered: