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
Having an issue with not being able to read the output of a win program spawned in node:
exec('ipconfig.exe', (e, stdout, err) => { console.log(stdout) //returns a blank line console.log(e) //returns null })
similarly with spawn:
const proc = spawn('ipconfig.exe'); proc.stdout.on('data', data => { //never gets called });
I'm not sure how interop is supposed to work but is this expected behavior?
The text was updated successfully, but these errors were encountered:
Can you please fill out the template? There's a lot of helpful information in there for triaging issues.
Sorry, something went wrong.
I believe this is a duplicate of #1840
ah yes sorry i missed #1840. that's the exact issue. closing this
No problem! Issue is fixed in the most recent Insider fast build I believe.
No branches or pull requests
Having an issue with not being able to read the output of a win program spawned in node:
similarly with spawn:
I'm not sure how interop is supposed to work but is this expected behavior?
The text was updated successfully, but these errors were encountered: