Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can't find Node

Mark
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 26, 2025

Windows 11.
Windows Powershell (5) + Powershell 7

Node is installed in default location: C:\Program Files\nodejs - which is in my user and system Path and can be found in the terminal normally:

node --version
v22.17.0

Rovo Dev (acli) can't find or run node.

Prompt: get the node version

Response:  I'll help you check the Node.js version in the workspace. Let me run a command to get this information. │
└── Calling powershell: {"command": "node --version"}

| ~~~~
| The term 'node' is not recogniz...
| spelling of the n...

Log:

Node.js doesn't seem to be in the PATH. Let me check if there are any Node.js installations in common locations:

Regular terminal finds it just fine and no problem from VSCode.

1 comment

Comment

Log in or Sign up to comment
Jovana Dunisijevic
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 1, 2025

Hi @Mark 

 

Thanks for sharing the details! This is a known issue on Windows: sometimes, when Rovo Dev CLI runs commands, it uses a different environment than your regular terminal or VSCode, so it might not see Node.js in your PATH—even if you can run node --version yourself.

Quick fix:
Try launching your terminal as an administrator and then run the CLI again. If that doesn’t help, you can add the Node.js path directly to your system environment variables (not just user variables), then restart your computer. This usually makes Node.js visible to all processes, including those started by Rovo Dev CLI.

Let us know if this helps!

Kindest regards,

Jov

TAGS
AUG Leaders

Atlassian Community Events