Angular 8与ASP.NET Core分离项目刷新页面报错：找不到npm-cli.js

Hey there, let's break down what's causing this error and walk through how to fix it step by step!

错误核心原因 #

From the error message Error: Cannot find module 'C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js', the root issue is that your system can't locate npm's core execution file. Here are the most common triggers:

• Your Node.js or npm installation is corrupted, so the npm-cli.js file is missing or the path is incorrect
• Your system's environment variables are misconfigured, pointing to a wrong Node.js/npm directory
• The npm dependencies for your Angular project aren't installed properly, or ASP.NET Core is running the npm command from the wrong working directory
• Permission issues are preventing the process from accessing the npm installation folder

Step-by-Step Fixes #

1. Verify Node.js & npm Integrity #

First, open Command Prompt or PowerShell and run these commands:

node -v
npm -v

If npm -v throws the same "cannot find module" error, your npm installation is definitely corrupted.

• Fix: Reinstall Node.js (download the correct version from the official site, choose the "Repair" option during installation, or just do a fresh overwrite install). After reinstalling, run npm -v again to confirm it works.

2. Check Environment Variables #

Make sure your system's PATH environment variable includes the correct Node.js installation directory (usually C:\Program Files (x86)\nodejs or C:\Program Files\nodejs), and this path is placed early in the list to avoid being overridden by old Node.js versions.

• How to do it: Right-click "This PC" → Properties → Advanced System Settings → Environment Variables → Find PATH in System Variables → Edit to check if the correct Node.js path exists. Add it if missing, or adjust the order if there's a conflicting path.

3. Repair npm (If Node Works but npm Doesn't) #

If node -v works but npm -v still errors, try repairing npm globally:

npm install -g npm

This forces an update of the global npm version and fixes any corrupted files.

4. Check ASP.NET Core SPA Configuration #

Since you're using ASP.NET Core with Angular, the backend uses Microsoft.AspNetCore.SpaServices to call npm commands. Check your project's configuration:

• In Startup.cs (or Program.cs for .NET 6+), verify that UseAngularCliServer or UseProxyToSpaDevelopmentServer is set up correctly. Make sure it's using the start script, and your Angular project's package.json has a valid start script (usually "start": "ng serve").
• Also, confirm that ASP.NET Core is running from the correct working directory so npm can find your Angular project's package.json.

5. Reinstall Angular Dependencies #

Navigate to your Angular project's root folder (where package.json lives) and run:

npm cache clean --force
npm install

First, we clear the npm cache to fix any corrupted cached files, then reinstall all dependencies from scratch.

6. Fix Permission Issues #

If all else fails, permission problems might be blocking access to the npm installation folder. Try running Command Prompt/PowerShell as Administrator, then re-run your npm commands or start the ASP.NET Core project.

内容的提问来源于stack exchange，提问作者kianoush dortaj