Photo by Markus Spiske 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. This garbage shows up in my terminal:

npm warn saveError ENOENT: no such file or directory, open '/home/user/myproject/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 '/home/user/myproject/package.json'
npm warn myproject No description
npm warn myproject No repository field.
npm warn myproject No README data
npm warn myproject No license field.

Nothing works. Your dependencies aren't installing. Node has no idea what your project even is. The npm ENOENT package.json missing error is one of those things that looks scary at first but is almost always caused by something embarrassingly simple. Almost always.

Let me walk you through what's actually going on and how to get unstuck.

Why This Error Happens

ENOENT literally stands for "Error NO ENTry" — which is Unix-speak for "that file doesn't exist." When npm tries to read or update your package.json and can't find it, it throws this error. The most common reasons I've seen:

You're in the wrong directory. Honestly, this is the culprit like 60% of the time. You think you're inside your project folder but you're actually one level up, or in a totally different path. It's embarrassing but we've all done it at 2am.

The package.json file genuinely doesn't exist yet. Maybe you cloned a half-finished repo, or someone forgot to commit the file, or you're starting a brand new project from scratch and haven't initialized it.

A typo in your folder name or path. Especially on Linux where paths are case-sensitive. MyProject and myproject are two completely different directories.

Now here's where it gets tricky — sometimes the error also shows up mid-project after a botched file operation, or if someone on your team accidentally added package.json to .gitignore. I've seen that happen. It's a painful conversation.

Fix 1: Make Sure You're Actually In the Right Directory

Before anything else, just verify where you are:

pwd

Then check what's in the folder:

ls -la

If you don't see a package.json listed there, that's your answer. Navigate into your actual project folder:

cd path/to/your/project
npm install

Sounds too simple, right? It is. But I can't tell you how many GitHub issues and Stack Overflow posts are basically just "I was in the wrong folder." Check this first before you go spiraling into dependency hell.

Fix 2: Initialize a Fresh package.json

If you've confirmed you're in the right place and there genuinely is no package.json, you need to create one. You've got two options here depending on how patient you're feeling.

The quick-and-dirty way — this just accepts all the defaults without asking you anything:

npm init -y

This spits out a basic package.json with your folder name as the project name, version 1.0.0, and a bunch of empty fields. Good enough to get moving. After that, run your npm install again and you should be back in business.

If you actually care about filling in the metadata (name, description, license, etc.), use the interactive version:

npm init

It'll walk you through each field. Hit enter to skip anything you don't care about right now.

Fix 3: Restore a Missing package.json From Git

Here's a scenario I've run into more than once — you're working on an existing project, the package.json was there before, and now it's mysteriously gone. Maybe someone deleted it accidentally, or a bad merge blew it away.

If your project is tracked with Git, you can restore it:

git checkout HEAD -- package.json

That pulls the last committed version of the file back from history. If that doesn't work because the deletion was committed, you can dig into git log to find a commit where it existed:

git log --oneline -- package.json

Find the commit hash where it was last present, then:

git checkout <commit-hash> -- package.json

This is honestly a lifesaver. I've had juniors on my team panic-delete files thinking they were junk, and git log has saved the day more times than I can count.

(Side note: if you're not committing your package.json to version control, please start. It's not optional. That file is the heartbeat of your Node project.)

Fallback: Manually Create a Minimal package.json

If you're in a situation where git isn't available and npm init is somehow failing on you — maybe you're in a restricted environment or a Docker container mid-build — you can just create a bare-minimum package.json by hand:

{
  "name": "my-app",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "start": "node index.js"
  },
  "dependencies": {}
}

Save that as package.json in your project root. It's not pretty, but npm will accept it and you can run npm install <package-name> to start adding your actual dependencies again. Think of it as a patch job — get the project breathing, then clean it up properly later.

One More Thing to Double-Check

If you're using a monorepo setup or a tool like Nx, Turborepo, or Yarn Workspaces, make sure you're running npm commands from the correct workspace package directory, not just the root. The root package.json exists, but each sub-package needs its own. Workspaces can confuse people who are new to them — and honestly the error messages don't make it any more obvious.

Also worth checking: if you're inside a Docker build and hitting this error, verify your COPY instruction in the Dockerfile is actually copying package.json before you run npm install. Something like:

COPY package*.json ./
RUN npm install

Missing that step is a classic Docker gotcha with Node apps.

Alright, so to recap the quick hits — check your directory first, initialize if needed, restore from git if it vanished, and hand-write a minimal file as a last resort. Nine times out of ten you'll be done after step one or two. Hope this saves you some time and maybe a little sanity.

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