-
Notifications
You must be signed in to change notification settings - Fork 286
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
Cannot read output from another node process installed with snap #2713
Comments
That's almost certainly caused by snap's security sandbox. Try getting in touch with the maintainer of the node snap, he or she can probably provide more details. |
The problem is only when node reads output of another node. |
Added issue here: nodesource/distributions#1053 |
@angryziber - is this resolved? |
inactive, closing. feel free to re-open if it is outstanding |
When node is installed via snap (14/stable channel).
execSync('node something').toString()
always returns an empty string with no errors.This is a problem as many transforming packages use this trick to deasync processing.
execSync('node something', {stdio: 'inherit'}).toString()
would correctly display the output in parent process's stdout, but there is no way of capturring it.
If node is installed via deb package, there is no such problem.
Makes jest/etc unusable in many cases.
The text was updated successfully, but these errors were encountered: