How to fix npm ERR! code ENOENT npm ERR! prepublish-only No files to publish in npm

What this error means

This error occurs when npm publish (or npm version with prepublishOnly script) cannot find any files to include in your package tarball. npm uses three mechanisms to determine what gets published: 1. **files field** (allowlist) - only listed files are published 2. **.npmignore** (denylist) - excludes files from publication 3. **.gitignore** (fallback denylist) - used if no .npmignore exists When all mechanisms filter out your actual code, the package ends up empty except for metadata files like package.json and README. The "ENOENT" (Error: NO ENTry) code indicates that required file(s) do not exist in the paths npm is looking for.

Typical symptoms

• npm publish or npm version fails with 'ENOENT: no such file or directory'
• Published package on npm registry contains only README, LICENSE, and package.json
• Build script output (like dist/ or lib/) doesn't appear in the published package
• npm pack produces a tarball with minimal files
• Installing your package provides only metadata, not actual code

Common causes

1. files field in package.json doesn't include your compiled output directory
2. .gitignore excludes build artifacts (dist/, lib/) and no .npmignore exists to override
3. .npmignore file exists but doesn't properly include necessary directories
4. prepublishOnly or build script generates files but package.json files field points to non-existent paths
5. Build step isn't run before npm publish in CI pipeline
6. Main entry point in package.json references a file that doesn't exist

How to fix "npm ERR! code ENOENT npm ERR! prepublish-only No files to publish"

npm pack
tar -tzf your-package-1.0.0.tgz

{
  "name": "my-package",
  "main": "dist/index.js",
  "files": [
    "dist",
    "README.md",
    "LICENSE"
  ]
}

node_modules
.git
src
test
*.log
.env

{
  "scripts": {
    "build": "tsc",
    "prepublishOnly": "npm run build"
  }
}

{
  "main": "dist/index.js",
  "types": "dist/index.d.ts",
  "exports": {
    ".": {
      "import": "./dist/index.mjs",
      "require": "./dist/index.js"
    }
  }
}

Advanced notes

Frequently asked questions

What does "npm ERR! code ENOENT npm ERR! prepublish-only No files to publish" mean?

This error occurs when npm publish (or npm version with prepublishOnly script) cannot find any files to include in your package tarball. npm uses three mechanisms to determine what gets published: 1. files field (allowlist) - only listed files are published 2.

How do I fix "npm ERR! code ENOENT npm ERR! prepublish-only No files to publish"?

This error occurs when npm publish cannot find any files to include in your package tarball. npm uses the files field in package.json as an allowlist, .npmignore as a denylist, or .gitignore as a fallback. When all mechanisms filter out your code, the package ends up empty.

What causes "npm ERR! code ENOENT npm ERR! prepublish-only No files to publish"?

files field in package.json doesn't include your compiled output directory .gitignore excludes build artifacts (dist/, lib/) and no .npmignore exists to override .npmignore file exists but doesn't properly include necessary directories

Is the "npm ERR! code ENOENT npm ERR! prepublish-only No files to publish" error serious?

Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Related errors

• npm ERR! code E404 npm ERR! 404 Not Found - PUT https://registry.npmjs.org/package - Package not found

  How to fix "404 Not Found - PUT" when publishing to npm

  HIGH

• npm ERR! code E403 npm ERR! 403 Forbidden - PUT - Package name too similar to existing packages

  How to fix "Package name too similar to existing packages" in npm

  MEDIUM

• npm ERR! code EOTP npm ERR! This operation requires a one-time password

  How to fix "This operation requires a one-time password" in npm

  MEDIUM

• npm WARN publish npm WARN publish No license field

  How to fix "No license field" in npm

  MEDIUM

• npm ERR! code EAI_AGAIN

  How to fix "EAI_AGAIN" in npm

  MEDIUM

• npm ERR! code EPERM npm ERR! This operation requires administrator privileges

  How to fix "EPERM: This operation requires administrator privileges" in npm

  MEDIUM

Official resources & further reading

• 📚npm Official Documentation
• 📖
  Docs: package.json files field(Official Docs)
• 💬
  SO: npm publish no files(Stack Overflow)