Inconsistent Package Version Display in Ionic VS Code Plugin

[joptimus]

Description: The Ionic VS Code plugin exhibits inconsistent behavior regarding package version display between the Windows and Mac versions. On Windows, when viewing the packages, only the currently installed version is shown without any indication of a higher stable version. Conversely, the Mac version displays the latest stable version available for upgrade.

Steps to Reproduce:

1. Install the Ionic VS Code plugin.
2. Create a new blank Angular project using the extension.
3. View the package information.

Expected Behavior: On both Windows and Mac, the package information should be displayed consistently, showing the latest stable version available for upgrade.

Actual Behavior: On Windows:

• An error message appears in the Output panel:[error] Unable to run 'npm outdated'. Try reinstalling node modules (npm install).
• The Ionic package is displayed as version 7.0.0, without any additional information.

On Mac:

• No error message is displayed.
• The Ionic package is displayed as version 7.0.0, accompanied by an arrow indicating version 7.0.7 as the latest stable version.

Additional Information: The issue was reproducible by following the steps above. Also I can separately run the command npm outdated inside the terminal and it works

Environment:

• Ionic VS Code plugin version: 1.41.0
• Operating System: Windows 10 19045.2965 / macOS 12.6.5
• Node.js version: 16.15.1
• npm version: 8.11.0

[dtarnawsky]

Thanks for the bug report @joptimus, I'll take a look at this today to see if can easily reproduce. One thing to try is to remove node_modules and re-run npm install to see if this fixes the problem.

[joptimus]

@dtarnawsky I just tried this and still same issue. I can run npm outdated inside the project and it will display the packages and latest versions. I also updated to npm version 9.6.6 to see if that had any impact however it still displays same issue.

[dtarnawsky]

Hey @joptimus, can you choose Help > Toggle Developer Tools and see what the real error that is logged when npm outdated is run. In testing out on Windows I don't see this issue but it may be something with the way I have node installed.

[joptimus]

@dtarnawsky here is what the console readout shows when I open the extension

[joptimus]

Here is when I reloaded VSCode and opened it again

[dtarnawsky]

That looks like it's a bad install of Node on a Windows machine. There's a stack overflow post on how to fix this: https://stackoverflow.com/questions/72401421/message-npm-warn-config-global-global-local-are-deprecated-use-loc

Alternatively, I would recommend uninstalling Node (and make sure c:\program files\nodejs is deleted) then reinstall.

[joptimus]

Thank you @dtarnawsky ! I uninstalled Node and reinstalled, everything works good now