How to fix npm ERR! code EREGISTRYMISSING npm ERR! Missing registry configuration in npm

npmINTERMEDIATEHIGHUpdated Dec 5, 2025· 154 views

This error occurs when npm cannot find or access the registry configured for a package, typically due to missing .npmrc configuration, incorrect registry URLs, or authentication issues. npm needs a valid registry URL to download packages.

Quick fix

Fixes npm ERR! code EREGISTRYMISSING npm ERR! Missing registry configuration

npm config list
  1. Check your current npm registry configuration
  2. Set the default npm registry to the public registry
  3. Create or update your .npmrc file for scoped packages
  4. Clear npm cache and retry installation
npm — error
npm config list
npm ERR! code EREGISTRYMISSING
npm ERR! Missing registry configuration

What this error means

The EREGISTRYMISSING error means npm is unable to locate or connect to the package registry required to install a package. This commonly happens with scoped packages (like @mycompany/package-name) that require a custom private registry, but npm doesn't have the registry configuration in its .npmrc file. The error can also occur when the default npm registry URL is missing, corrupted, or unreachable. npm needs to know which registry server to contact to fetch package metadata and code. Without this configuration, npm cannot proceed with installation. For scoped packages, npm looks for a specific registry URL in the .npmrc file prefixed with the scope name.

Typical symptoms

  • npm install fails immediately with EREGISTRYMISSING error before attempting to download any packages
  • Error occurs specifically when installing scoped packages (e.g., @mycompany/package-name) but not with public packages
  • Works in one environment but fails in another (e.g., local vs CI/CD pipeline)
  • Error persists after updating package.json and package-lock.json is deleted
  • Private packages show as 404 or cannot be found even though they exist in your registry

Common causes

  1. Missing .npmrc file in the project root or home directory with required registry configuration
  2. Scoped package registry not configured - the scope (@mycompany) is not associated with a private registry URL in .npmrc
  3. Incorrect .npmrc syntax - using @scope=url instead of @scope:registry=url
  4. .npmrc file in wrong location or with wrong file extension (e.g., .npmrc.txt on Windows)
  5. Default npm registry URL removed or corrupted from npm configuration

How to fix "npm ERR! code EREGISTRYMISSING npm ERR! Missing registry configuration"

1Check your current npm registry configuration

First, verify what registry npm is currently configured to use:

bash
npm config list

Look for the registry line in the output. It should show something like:

bash
registry = "https://registry.npmjs.org/"

If you don't see a registry line or see an error, npm is missing registry configuration.

2Set the default npm registry to the public registry

If the registry is missing or corrupted, set it back to the official npm registry:

bash
npm config set registry https://registry.npmjs.org/

For scoped packages that use a private registry, also configure the scope:

bash
npm config set @mycompany:registry https://your-private-registry.com/

Verify the configuration was set correctly:

bash
npm config get registry
3Create or update your .npmrc file for scoped packages

For projects using private registries, create a .npmrc file in your project root:

bash
# For public packages from npm
registry=https://registry.npmjs.org/

# For scoped private packages
@mycompany:registry=https://your-private-registry.com/

# Authentication token for private registry
//your-private-registry.com/:_authToken=YOUR_AUTH_TOKEN_HERE

IMPORTANT:
- File must be named exactly .npmrc (not .npmrc.txt)
- Use correct syntax: @scope:registry= not @scope=
- Auth tokens must be prefixed with // and include _authToken

4Clear npm cache and retry installation

After updating your registry configuration, clean the npm cache and attempt installation again:

bash
npm cache clean --force

rm package-lock.json
rm -rf node_modules/

npm install

Or specify the registry directly in the install command:

bash
npm install --registry=https://registry.npmjs.org/
5Verify authentication and registry accessibility

If you're using a private registry, verify you're logged in and the registry is accessible:

bash
npm login --registry=https://your-private-registry.com/ --scope=@mycompany

curl -H "Authorization: Bearer YOUR_TOKEN" https://your-private-registry.com/

npm cache verify

For GitHub Packages, use a GitHub personal access token with read:packages permissions.

Advanced notes

On Windows, the .npmrc file must be created via command line or a code editor (not Windows Explorer) because Windows doesn't natively support files with only a dot prefix. A common mistake is the file being saved as .npmrc.txt instead. On macOS, TextEdit may save as .npmrc.rtf with garbage characters - use VSCode or command line instead. For CI/CD environments, pass credentials securely via environment variables rather than hardcoding tokens in .npmrc files.

Frequently asked questions

What does "npm ERR! code EREGISTRYMISSING npm ERR! Missing registry configuration" mean?
The EREGISTRYMISSING error means npm is unable to locate or connect to the package registry required to install a package. npmrc file. The error can also occur when the default npm registry URL is missing, corrupted, or unreachable.
How do I fix "npm ERR! code EREGISTRYMISSING npm ERR! Missing registry configuration"?
This error occurs when npm cannot find or access the registry configured for a package, typically due to missing .npmrc configuration, incorrect registry URLs, or authentication issues. npm needs a valid registry URL to download packages.
What causes "npm ERR! code EREGISTRYMISSING npm ERR! Missing registry configuration"?
Missing .npmrc file in the project root or home directory with required registry configuration Scoped package registry not configured - the scope (@mycompany) is not associated with a private registry URL in .npmrc Incorrect .npmrc syntax - using @scope=url instead of @scope:registry=url
Is the "npm ERR! code EREGISTRYMISSING npm ERR! Missing registry configuration" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading