Back to error codes
ERROR ENOTFOUND
npm ENOTFOUND, Registry Not Found
npm/pnpm Error
npm cannot connect to the package registry.
Root Cause
No internet connection, the npm registry is down, a corporate proxy is blocking the connection, or a custom registry URL is misconfigured.
How to Fix
Check your internet connection. Verify the registry URL: npm config get registry. If behind a proxy, configure npm proxy settings.
Quick Summary
npm ENOTFOUND means the registry is unreachable. Check internet connectivity, verify the registry URL, and configure proxy settings if behind a corporate firewall.
Key Takeaways
Key Takeaways
- Check internet connection first
- Verify registry: npm config get registry (should be https://registry.npmjs.org/)
- Configure proxy: npm config set proxy http://proxy:port
- Use npm cache clean --force if the cache is corrupted
Use Cases
When to use it
- No internet connection
- Corporate proxy blocking npm
- Custom registry URL misconfigured
Watch out
Common Mistakes
- Not checking if a custom registry is configured: npm config get registry
- Not configuring proxy settings in corporate environments
FAQ
ENOTFOUND npm ENOTFOUND, Registry Not Found, Frequently Asked
How do I use a private npm registry?
npm config set registry https://your-registry.com or add .npmrc to your project: registry=https://your-registry.com
Still having issues?
Check your network logs or use our developer tools to inspect headers, decode tokens, or validate your requests.