安装Git与Node后执行Angular CLI全局安装出现警告问题求助

Hey there! I’ve run into these exact warnings a bunch of times when setting up Angular projects—let’s walk through the most common fixes to get your project running smoothly.

One of the most frequent causes of warnings is a version mismatch between Node.js and Angular CLI. Angular has strict Node version requirements for each release, so let’s check first:

• Run node -v to get your current Node.js version
• Run ng version to see your global Angular CLI version and the project’s Angular version

Compare your Node version against the official Angular requirements (e.g., Angular 16 needs Node 16.14+, Angular 17 requires Node 18.13+). If they don’t match:

• Use a version manager like nvm (Node Version Manager) to install the correct Node version (this is the cleanest approach)
• Or downgrade/upgrade your global Angular CLI to match your project: npm install -g @angular/cli@<your-project-angular-version>

If you’re seeing EACCES or permission-related warnings when running npm commands, it’s because your user account doesn’t have access to the global npm package directory. Here’s how to fix it:

Option 1: Configure npm to use a user-specific directory #

# Create a global npm directory in your home folder
mkdir ~/.npm-global
# Set npm to use this directory
npm config set prefix '~/.npm-global'

Then add this directory to your system PATH (edit ~/.bashrc, ~/.zshrc, or ~/.profile depending on your shell):

export PATH=~/.npm-global/bin:$PATH

Save the file and run source ~/.bashrc (or the corresponding file for your shell) to apply the changes.

Option 2: Use nvm to manage Node versions #

nvm installs Node.js and npm in your user directory by default, eliminating permission issues entirely. Just install nvm, then use nvm install <required-node-version> to switch to the correct version.

Corrupted cache or outdated lock files often trigger warnings. Let’s do a clean reinstall:

1. Delete the existing node_modules folder and package-lock.json file:

   # On macOS/Linux
   rm -rf node_modules package-lock.json
   # On Windows (Command Prompt)
   rmdir /s /q node_modules
   del package-lock.json
   

2. Clear the npm cache:

   npm cache clean --force
   

3. Reinstall all dependencies:

   npm install
   

4. Try running your project again:

   ng serve
   

Peer dependency warnings happen when a package expects a specific version of another package, but your project has a different version installed. For example, you might see something like:

Warning: @angular/common@16.2.0 requires a peer of rxjs@~7.8.0 but rxjs@8.0.0 is installed.

To fix this:

• Install the exact required version of the peer dependency:

  npm install rxjs@~7.8.0
  

• If you need to bypass the check temporarily (not recommended for long-term use), run:

  npm install --legacy-peer-deps
  

If your global CLI version doesn’t match the one used in your project, you’ll get version mismatch warnings. To fix this:

1. Install the project-specific CLI version locally:

   npm install @angular/cli@<your-project-angular-version> --save-dev
   

2. Run the project using the local CLI (instead of the global one):

   npx ng serve
   

If none of these fixes work, sharing the exact warning messages would help narrow down the issue further!

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