Absolutely! You can totally set up a project-specific NPM proxy that won’t mess with your global settings—and this is actually a fantastic practice to help other developers get up and running quickly on your project. Let’s break down the best ways to do this:

1. Use a Local .npmrc File (Recommended) #

This is the go-to method because it’s version-controllable, so every developer on your team gets the proxy config automatically when they clone the project.

• Navigate to your project’s root directory and create a file named .npmrc
• Add your proxy details (replace placeholders with your actual proxy info):

  # HTTP proxy
  proxy=http://your-proxy-host:port/
  # HTTPS proxy (often same as HTTP)
  https-proxy=http://your-proxy-host:port/
  # Optional: If your proxy requires authentication
  proxy-auth=your-username:your-password
  https-proxy-auth=your-username:your-password
  # Optional: Skip proxy for internal domains/localhost
  no-proxy=localhost,127.0.0.1,your-internal-domain.com
  

• Commit this file to your version control system (like Git). Now anyone working on the project will inherit this proxy config automatically—no manual setup required.

2. Temporary Environment Variables (For Sensitive Credentials) #

If you don’t want to commit proxy credentials to version control, use session-specific environment variables. These only apply to your current terminal session:

• Linux/macOS:

  export HTTP_PROXY=http://your-proxy-host:port/
  export HTTPS_PROXY=http://your-proxy-host:port/
  # For authenticated proxies
  export HTTP_PROXY=http://username:password@your-proxy-host:port/
  export HTTPS_PROXY=http://username:password@your-proxy-host:port/
  

• Windows (Command Prompt):

  set HTTP_PROXY=http://your-proxy-host:port/
  set HTTPS_PROXY=http://your-proxy-host:port/
  

• Windows (PowerShell):

  $env:HTTP_PROXY="http://your-proxy-host:port/"
  $env:HTTPS_PROXY="http://your-proxy-host:port/"
  

• To make this easier for your team, save these commands into a script file (like setup-proxy.sh for Unix systems or setup-proxy.bat for Windows) and add it to your project. Team members just need to run the script once per terminal session.

3. Configure via npm config Command #

You can also use the npm config tool to generate the project-specific .npmrc file directly:

# Set HTTP proxy
npm config set proxy http://your-proxy-host:port/ --userconfig ./your-project/.npmrc
# Set HTTPS proxy
npm config set https-proxy http://your-proxy-host:port/ --userconfig ./your-project/.npmrc
# Optional: Add no-proxy list
npm config set no-proxy "localhost,127.0.0.1" --userconfig ./your-project/.npmrc

This does the exact same thing as manually editing the .npmrc file—just a command-line alternative.

Quick Tip #

If a team member already has a global proxy set up, don’t worry! The project-specific .npmrc takes precedence over global settings, so their global config won’t interfere with this project.

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