npm install fails with 'npm ERR! code ENOENT' / 'npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open .../package.json'. What is wrong?

Cause: npm looks for a package.json in the directory you ran the command from. ENOENT means "no such file", so the command ran in a folder that is not a project root (a parent folder, your home directory, a cloned repo's wrong subfolder), or the project simply has no package.json yet. When npm cannot find one in the current folder it also considers the nearest parent folder that has a package.json or node_modules, which can make the failing path look surprising. Fix (best first): 1. Print where you are with pwd (or cd on Windows) and list files with ls. Change into the folder that actually contains package.json (often a subfolder such as app/, frontend/ or server/), then rerun the command. 2. In a monorepo, run the command from the package folder, or target it from the root with the workspace option, for example npm run build --workspace=<package-name>. 3. If this is a new project with no package.json, create one with npm init (npm init -y accepts the defaults), then install packages. 4. In scripts, CI or Dockerfiles, make the working directory explicit (WORKDIR in a Dockerfile, working-directory in a CI step) and make sure package.json is copied in before npm install runs, for example COPY package*.json ./ followed by RUN npm ci. 5. Check that the path is not blocked by a typo, wrong case on Linux, or a .dockerignore / .gitignore pattern that excludes package.json from the build context. Verify: ls package.json succeeds in the folder, and npm install (or npm ci) starts resolving dependencies instead of printing ENOENT. Sources: https://docs.npmjs.com/cli/v10/commands/npm-install https://docs.npmjs.com/cli/v10/using-npm/config https://docs.npmjs.com/cli/v10/configuring-npm/package-json