How to fix npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/create-something in npm

npmINTERMEDIATEMEDIUMUpdated Dec 3, 2025· 139 views

The E404 error occurs when npm cannot find a package in the registry. The most common cause is a typo in the package name, but it can also indicate registry configuration issues or private package access problems.

Quick fix

Fixes npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/create-something

# Search for the package
npm search create-react-app

# Or visit https://www.npmjs.com/search?q=your-package
  1. Verify the package name
  2. Check registry configuration
  3. For scoped/private packages
  4. Clear cache and retry
npm — error
# Search for the package
npm search create-react-app
# Or visit https://www.npmjs.com/search?q=your-package
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/create-something

What this error means

This error indicates npm queried the npm registry for a package and received a 404 HTTP response—the package doesn't exist at that URL. Common scenarios: 1. **Typo in package name**: "creat-react-app" instead of "create-react-app" 2. **Package was renamed or removed**: Old name no longer works 3. **Private/scoped package**: Requires authentication or different registry 4. **Wrong registry configured**: .npmrc pointing to wrong registry The error message shows the exact URL npm tried, which helps identify the issue.

Typical symptoms

  • npm install fails with 404 error
  • Error message shows registry URL and package name
  • Same package installs fine for others
  • Works from one network but not another

Common causes

  1. Typo in package name (most common)
  2. Package doesn't exist on npm registry
  3. Package is private/scoped requiring auth
  4. Registry misconfigured in .npmrc
  5. Package was unpublished or renamed

How to fix "npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/create-something"

1Verify the package name

Check exact spelling on npmjs.com:

bash
# Search for the package
npm search create-react-app

# Or visit https://www.npmjs.com/search?q=your-package

Common typos:
- creat-react-app → create-react-app
- expresss → express
- lodash_ → lodash

2Check registry configuration

Verify your registry is correct:

bash
# Check current registry
npm config get registry
# Should be: https://registry.npmjs.org/

# Reset if wrong
npm config set registry https://registry.npmjs.org/
3For scoped/private packages

Configure registry for scoped packages:

bash
# Set registry for scope
npm config set @mycompany:registry https://npm.pkg.github.com

# Authenticate
npm login --registry https://npm.pkg.github.com

In .npmrc:

bash
@mycompany:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=YOUR_TOKEN
4Clear cache and retry

Clear npm cache in case of stale data:

bash
npm cache clean --force
npm install package-name
5Test registry connectivity

Verify you can reach the registry:

bash
npm ping
# Should respond with registry info

# View package info
npm view express

If ping fails, check network/firewall/VPN settings.

Advanced notes

Tips for avoiding 404 errors:

1. Copy package names from npmjs.com rather than typing from memory
2. Use npm search before installing unfamiliar packages
3. Check package.json of example projects for correct names
4. For scoped packages, ensure @ symbol is included: @babel/core not babel/core

For CI/CD with private packages:

yaml
# GitHub Actions
env:
  NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
run: |
  echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" >> .npmrc
  npm install

Frequently asked questions

What does "npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs" mean?
This error indicates npm queried the npm registry for a package and received a 404 HTTP response—the package doesn't exist at that URL. Common scenarios: 1. Typo in package name: "creat-react-app" instead of "create-react-app" 2.
How do I fix "npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs"?
The E404 error occurs when npm cannot find a package in the registry. The most common cause is a typo in the package name, but it can also indicate registry configuration issues or private package access problems.
What causes "npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs"?
Typo in package name (most common) Package doesn't exist on npm registry Package is private/scoped requiring auth
Is the "npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading