Error AtlasError Documentation and Resolution
Back to searchMore npm errors

npm

npm could not read package.json

npm ERR! enoent Could not read package.json

npm cannot find the package manifest in the current working directory, so install and build commands stop before dependency resolution starts.

ENOENTpackage managers

Observed message

npm ERR! enoent Could not read package.json

Why it happens

  • The command is running from the wrong folder.
  • The project is missing its package.json file.
  • A script or CI step changed directories before invoking npm.

How to fix it

  1. Run pwd and confirm you are inside the intended project root.
  2. Restore or recreate package.json if it was deleted or never committed.
  3. Review CI scripts and shell steps to ensure npm runs from the repository root.

Related errors

cb() never called!npm cb() never called when using shrinkwrapped dependenciesENOGIT / not found: gitnpm could not find gitENOSPCnpm could not write because the drive is full or not writableEACCES permissions errornpm EACCES permissions error during global install

Explore more

npmBrowse more npm errorspackage managersBrowse more package managers errors
npm ERR! enoent Could not read package.json: causes and fixes | Error Atlas