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
v14.17.6
Linux steven-ubuntu 5.11.0-37-generic #41~20.04.2-Ubuntu SMP Fri Sep 24 09:06:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
No response
const root = require("child_process") .execSync("node -v") .toString(); console.log(root);
I expected the output is the v14.17.6, but I got nothing.
const root = require("child_process") .execSync("node -v", {stdio:"inherit"})
In this case, I got the output in console.
It is so strange... Can anyone help me? I tried to search, about this case. But I can't get any helpful information.
The text was updated successfully, but these errors were encountered:
It works fine for me with node v14.18.0 on Linux.
Sorry, something went wrong.
Why didn't I think of that? Thank you for your kindness. I will reply after trying it again with node v14.18.0
It works fine for me with node v14.18.0 on Linux :) sorry for wasting your time.
I have confirmed that the issue only occurs on nodes installed from snap. Thanks a lot. sorry again for wasting your time nodejs/snap#13
No branches or pull requests
Version
v14.17.6
Platform
Linux steven-ubuntu 5.11.0-37-generic #41~20.04.2-Ubuntu SMP Fri Sep 24 09:06:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
I expected the output is the
v14.17.6
, but I got nothing.In this case, I got the output in console.
It is so strange...
Can anyone help me?
I tried to search, about this case. But I can't get any helpful information.
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
No response
What do you see instead?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: