How to fix npm ERR! code EPRIVATE npm ERR! This package has been marked as private in npm

Edit your package.json and delete the line containing "private": true:

Before:

{
  "name": "my-package",
  "version": "1.0.0",
  "private": true
}

After:

{
  "name": "my-package",
  "version": "1.0.0"
}

Then run: npm publish

If publishing an organization-scoped package (@myorg/package-name):

1. Remove "private": true from package.json
2. Ensure your package.json name uses the scope:

{ "name": "@myorg/my-package" }

3. Publish with appropriate access level:
- For private (requires paid account): npm publish
- For public: npm publish --access public

If you want to publish to a private registry (GitHub Packages, Verdaccio, Artifactory):

1. Remove "private": true from package.json
2. Create or edit .npmrc with the appropriate registry:

Example for GitHub Packages:

//npm.pkg.github.com/:_authToken=YOUR_GITHUB_TOKEN
@yourorg:registry=https://npm.pkg.github.com/

3. Publish: npm publish

In a monorepo with workspaces:

1. Keep "private": true in the root package.json (prevents accidental root publication)
2. Remove "private": true from workspace packages that should be published

// Root package.json (keep private)
{ "private": true, "workspaces": ["packages/*"] }

// packages/my-lib/package.json (remove private)
{ "name": "@myorg/my-lib", "version": "1.0.0" }

Publish individual workspaces:

npm publish --workspace=packages/my-lib

If you want restricted access (not blocking publication):

npm Private Packages (paid):
- Requires paid npm account
- Only scoped packages can be private
- Publish with: npm publish

GitHub Packages (free):
- Free, no paid npm account required
- Configure .npmrc with GitHub token
- Collaborators need GitHub access to install

Remove "private": true and use registry access controls instead.