Actual behavior
After installing an NpmBasedCommandlet tool (e.g., Nest CLI), IDEasy’s output shows the current Node.js version as if it were the tool’s version (Nest), and it claims it “overwrote” a previous Nest version even though it did not. This is only a logging issue as the installation itself works correctly.
Reproduce
ide install nest
Expected behavior
After installing an NpmBasedCommandlet tool (e.g., Nest CLI), IDEasy should:
- Display the actual tool version that was installed (i.e., the npm package version such as @nestjs/cli’s version), not the current Node.js version.
- Only report “overwritten/updated” if a previous installation of that same tool existed and was actually replaced.
IDEasy status
IDE_ROOT is set to ~/projects
IDE_HOME is set to ~/projects/project
Your version of IDEasy is 2026.04.002.
Your are using the latest version of IDEasy and no update is available.
Your operating system is windows(10.0)@x64 [Windows 11@amd64]
You are online.
Found bash executable at: C:/Program Files/Git/usr/bin/bash.***
Found git executable at: C:/Program Files/Git/mingw64/bin/git.***
Your settings are up-to-date.
Related/Dependent issues
#1860
Comments/Hints
see #1860 (comment)
Actual behavior
After installing an
NpmBasedCommandlettool (e.g., Nest CLI), IDEasy’s output shows the current Node.js version as if it were the tool’s version (Nest), and it claims it “overwrote” a previous Nest version even though it did not. This is only a logging issue as the installation itself works correctly.Reproduce
ide install nest
Expected behavior
After installing an
NpmBasedCommandlettool (e.g., Nest CLI), IDEasy should:IDEasy status
Related/Dependent issues
#1860
Comments/Hints
see #1860 (comment)