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

Before publishing, run npm pack to generate a test tarball and inspect its contents:

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

This shows exactly which files will be in your published package. If your code files are missing, the ignore/files configuration is wrong.

If you have a files array in package.json, verify it includes your compiled output:

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

The files field is an allowlist—only files you explicitly list will be published. Common mistake: listing 'src' when you meant 'dist'.

The ignore files work as a denylist:

- If .npmignore exists, npm uses ONLY .npmignore (not .gitignore)
- If .npmignore doesn't exist, npm falls back to .gitignore
- They are NOT merged

If your .gitignore excludes build artifacts (dist/, lib/), add an .npmignore that doesn't:

node_modules
.git
src
test
*.log
.env

Or use the files field in package.json instead.

Add or verify a prepublishOnly script in package.json:

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

The prepublishOnly lifecycle hook runs before npm publish but NOT when someone installs your package. This ensures dist/ is populated before npm tries to pack it.

Check that package.json's main field points to a file that will exist after build:

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

If main points to src/index.js but you only ship dist/, users won't find the entry point.