How to fix npm ERR! code ENOENT npm ERR! Missing workspace package: packages/package-name in npm | DevErrors

How to fix "npm ERR! code ENOENT npm ERR! Missing workspace package: packages/package-name"

1Verify the workspace directory exists

Check if the missing directory actually exists:

bash

# List your packages directory
ls -la packages/

# Check if the specific package exists
ls -la packages/package-name

If the directory doesn't exist, either create it or remove it from workspaces config.

2Check your workspaces configuration

Verify the paths in your root package.json:

json

{
  "workspaces": [
    "packages/*"
  ]
}

Common mistakes:
- "packages" instead of "packages/*" (missing glob)
- "package/*" instead of "packages/*" (typo)
- Listing a specific package that doesn't exist

3Create the missing workspace

If you need to create the workspace:

bash

# Create workspace with npm init
npm init -w ./packages/package-name

# This creates the directory AND a package.json inside it

Or manually:

bash

mkdir -p packages/package-name
cd packages/package-name
npm init -y

4Ensure each workspace has package.json

Every workspace directory must contain a valid package.json:

bash

# Check for missing package.json files
for dir in packages/*/; do
  if [ ! -f "$dir/package.json" ]; then
    echo "Missing package.json in $dir"
  fi
done

Create missing package.json files:

bash

cd packages/missing-package
npm init -y

5Remove deleted workspaces from config

If the workspace was intentionally deleted, remove it from package.json:

json

{
  "workspaces": [
    "packages/core",
    "packages/cli"
  ]
}

Then clean and reinstall:

bash

rm -rf node_modules package-lock.json
npm install

Advanced notes

Empty directories in Git: Git doesn't track empty directories. If a workspace was added but never had files committed, cloning the repo won't create that directory. Use a .gitkeep file:

bash

touch packages/new-workspace/.gitkeep

Glob debugging: Test what your glob pattern matches:

bash

# See what packages/* would match
ls -d packages/*

Package name vs directory name: The workspace is identified by its directory path, not the name in its package.json. packages/my-app must exist even if package.json says "name": "@scope/my-app".

Symlinks: If workspaces are symlinked, ensure the symlink target exists. Use ls -la to see where symlinks point.

How to fix npm ERR! code ENOENT npm ERR! Missing workspace package: packages/package-name in npm

What this error means

Typical symptoms

Common causes

How to fix "npm ERR! code ENOENT npm ERR! Missing workspace package: packages/package-name"

Advanced notes

Related errors

Official resources & further reading