I’m facing an issue with the Angular CLI following the upgrade to Angular 20. The problem arises because the Angular CLI demands a version of Node.js that is newer than the one included with Visual Studio 2022.
While I have the latest Node.js installed globally, Visual Studio adds its own version to the beginning of the PATH. This means that when I attempt to execute ng build --watch via the NPM Task Runner (as specified in my package.json), it does not work due to the older Node version being prioritized from Visual Studio.
I have attempted to create a .cmd file to modify the PATH, but the ng.cmd file within node_modules\.bin\ behaves unexpectedly and still references the Visual Studio Node version.
I ran the where node command and received the following output:
where node
C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Microsoft\VisualStudio\NodeJs\node.exe
C:\Program Files\nodejs\node.exe
Is there a solution to this issue that doesn’t require me to use batch files to run npm run ... before launching Visual Studio? I have numerous projects, and I prefer not to alter the launch process for each one.
To resolve the issue with the Angular CLI after upgrading to Angular 20, navigate to Tools > Options > Projects and Solutions > Web Package Management > External Web Tools in Visual Studio. You will find Visual Studio’s Node.js path listed before the global PATH variable. Simply move the $(PATH) entry above the Visual Studio Node.js entry using the up arrow. This adjustment applies to all your projects, eliminating the need to configure them one by one. I encountered a similar problem, and this solution consistently allowed NPM Task Runner to utilize the global Node version, ensuring Angular CLI commands function seamlessly.
Had the same issue last month! Set NODE_PATH directly in your project properties - right-click project > properties > debugging > environment, then add NODE_PATH pointing to your global nodejs folder. VS will use your newer node version without messing with system paths or breaking other projects.
Here’s what worked for me - update Node.js directly in Visual Studio instead of messing with PATH variables. Download the newer Node version and manually replace the files in C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Microsoft\VisualStudio\NodeJs\. Just backup the original files first. This keeps VS integration working while giving you the Node version Angular 20 needs. It’s especially handy in corporate setups where IT policies reset your PATH changes, or when your teammates have different VS configs.