Photo by Ben Griffiths on Unsplash

So there I was, cloning a repo at some ungodly hour, running npm install like I've done a thousand times — and boom. Error. The kind that makes you squint at your screen and go "...seriously?" If you've ever seen something like this staring back at you, you know the feeling:

npm warn saveError ENOENT: no such file or directory, open '/Users/yourname/projects/myapp/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm warn enoent ENOENT: no such file or directory, open '/Users/yourname/projects/myapp/package.json'
npm warn myapp No description
npm warn myapp No repository field.
npm warn myapp No README data
npm warn myapp No license field.

The package.json not found error during npm install is one of those things that sounds catastrophic but is almost always something simple. I've debugged this for junior devs on my team probably a dozen times. Let me walk you through what's actually going on and how to get unstuck.

Why This Actually Happens

npm is looking for a package.json file in whatever directory you're currently sitting in. When it can't find one, it freaks out. The root causes basically come down to three things:

First — and this is the big one — you're just in the wrong directory. Sounds embarrassing but it happens to everyone. You cloned the repo, your terminal opened in the parent folder, and you ran npm install one level too high. npm is sitting there looking around like "uh, there's nothing here."

Second, the repo genuinely doesn't have a package.json. Maybe it's a backend-only project, a Python thing someone mislabeled, or a fresh repo where nobody committed the file yet. Worth checking.

Third — and this trips people up more than you'd think — the file exists but got corrupted or is malformed JSON. npm can't parse it, so it effectively treats it as missing.

Fix #1: Check Your Current Directory First (Seriously, Do This First)

Before anything else, run this:

pwd
ls -la

Or on Windows:

cd
dir

Look at what's actually in the folder. If you don't see a package.json listed, you're in the wrong place. Navigate into the actual project folder:

cd myapp
npm install

Honestly, nine times out of ten this is it. I've watched senior developers spend 10 minutes on this only to realize they were one directory level too high. No shame — it just happens.

Fix #2: Create a package.json If One Doesn't Exist

If you've confirmed you're in the right directory and there's genuinely no package.json, you need to create one. This is common when you're starting a fresh project or someone forgot to commit the file.

The quickest way is to let npm generate it for you:

npm init -y

The -y flag just accepts all the defaults so you're not sitting there hitting Enter fifteen times. It'll generate a basic package.json that looks something like this:

{
  "name": "myapp",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}

Now you can run npm install <package-name> to start adding your dependencies. If you had a list of packages you needed, just install them one by one or all at once and npm will populate the dependencies section automatically.

Fix #3: Validate and Repair a Corrupted package.json

Here's the thing though — sometimes the file IS there, it's just broken. A missing comma, a trailing comma after the last item, an unclosed bracket. JSON is annoyingly strict about this stuff.

Open the file and take a look:

cat package.json

If the output looks garbled or you spot something obviously wrong with the structure, you can validate it quickly using node itself:

node -e "require('./package.json')" && echo "Valid JSON"

If it throws a syntax error, node will tell you exactly which line is broken. Fix it, save it, run npm install again. There are also online JSON validators like jsonlint.com that make this even easier if you want to paste the whole thing in and get it highlighted for you.

(Side note: I once spent 20 minutes on a corrupted package.json that turned out to be a single trailing comma after the last dependency. One character. Twenty minutes. The JSON spec is not messing around.)

Fallback: Recover package.json from package-lock.json

This is a less common situation but worth knowing. If your package.json got deleted but you still have package-lock.json committed in your repo, you're not totally out of luck. The lock file contains a full record of your dependency tree.

You can't auto-generate a perfect package.json from it, but you can look inside package-lock.json and find the dependencies section to manually reconstruct what you need. Or, if you're working in a git repo, try recovering the file from your last commit:

git checkout HEAD -- package.json

That'll restore the last committed version of the file. If you haven't committed it yet... well, that's a lesson about committing your config files. We've all learned it the hard way.

Quick Sanity Checklist

If you're still stuck after all of this, run through these real quick:

• Are you running npm inside a Docker container or CI pipeline? The working directory might not be what you think it is.
• Did you clone with a shallow clone that might have missed files? Try git fetch --unshallow.
• Is your npm version ancient? Run npm -v and consider updating if you're on something prehistoric.

The npm install missing package.json error looks scary in the terminal but it's almost never a deep problem. Wrong directory covers probably 80% of cases. Hope this saves you from that 2am debugging spiral — been there, not fun.

Related: How to Fix npm Error Code ENOENT (and Why It Keeps Happening)