Edit This PageNPM Proxy
Repsy’s NPM Proxy feature allows your NPM repositories to act as intelligent proxies to external NPM registries like npmjs.org or private repositories.
An NPM proxy repository acts as an intermediary between your npm clients and external registries. When you install a package that doesn’t exist locally, the proxy automatically fetches it from the configured upstream registries and caches it for future use.
Setting Up NPM Proxy
Configuring Proxy Sources
You can configure multiple upstream registries with different priorities:
Public NPM Registry
Proxy URL: https://registry.npmjs.org
Private NPM Registry
Proxy URL: https://npm.your-company.com/repository/npm-private/
Username: your-username
Password: your-password
Common Configuration Options
For all proxy types, you can configure:
- SSL Validation: Enable/disable SSL certificate validation
- Connection Timeout: Set timeout in milliseconds (default: 5000ms)
- Active Status: Enable or disable the proxy
How NPM Proxy Works
Package Installation Flow
- Client Request: npm client requests a package from your
Repsyrepository. - Local Check:
Repsychecks if the package exists in local storage. - Proxy Fallback: If not found locally,
Repsyqueries configured proxies in priority order. - Authentication: Credentials are used if the proxy requires authentication.
- Caching: Downloads and caches the package for future requests.
- Response: Returns the package to the npm client.
Priority System
Proxies are queried in order of priority. If the first proxy fails or doesn’t contain the requested artifact, the next proxy in line is automatically tried. You can easily change the order of the proxies to customize the resolution priority.
Best Practices
- Set appropriate priorities based on package availability and speed.
- Disable unused proxies to reduce latency and avoid timeouts.
- Regularly update credentials for private registries.
Need Help?
Reach out to [email protected] if you need assistance configuring or troubleshooting NPM proxy functionality.
