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
TLDR;
node-red --version
v3.1.5
node-red --info
A reasonable request to show node-red version via command line was requested here: https://discourse.nodered.org/t/command-line-to-show-all-versions-running/85637
To add to that, the request also asks that additional (relevant) info be returned too e.g.
uname -r node -v npm -v node-red --version
As it is quite specific / different from a normal CLI where --version would be the norm, perhaps we could support this via something like --info?
--version
--info
NOTE: windows batch file should use ver instead of uname -r (it returns, for example "Microsoft Windows [Version 10.0.nnnnn.nnnn]")
ver
uname -r
NOTE: Trying to keep this simple as possible but useful for support folk who need to know specific info when triaging issues.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
TLDR;
node-red --version
that returns the version number e.g.v3.1.5
node-red --info
that returns version numbers of node, node-red, npm and OS infoA reasonable request to show node-red version via command line was requested here: https://discourse.nodered.org/t/command-line-to-show-all-versions-running/85637
To add to that, the request also asks that additional (relevant) info be returned too e.g.
As it is quite specific / different from a normal CLI where
--version
would be the norm, perhaps we could support this via something like--info
?NOTE: windows batch file should use
ver
instead ofuname -r
(it returns, for example "Microsoft Windows [Version 10.0.nnnnn.nnnn]")NOTE: Trying to keep this simple as possible but useful for support folk who need to know specific info when triaging issues.
The text was updated successfully, but these errors were encountered: