Error code
npm EPUBLISHCONFLICT
NPMEPUBLISHCONFLICT
Runtime Error Code· An error code from a programming runtime or package manager, like Node.js or npm.
What it means
The package version you are trying to publish already exists in the registry.
How to fix it
- Bump the version in package.json with npm version patch (or minor/major).
- Ensure you have not accidentally republished a version that was already released.
- Check the registry page for the package to confirm which versions exist.
Not affiliated with npm. Answer summarized from the manufacturer's manual linked above; consult that source for the authoritative procedure.
More npm codes
- E401Authentication is required to access this registry resource
- E403The registry rejected the request — you do not have permission to perform this action
- E404The requested package, version, or dist-tag was not found in the registry
- EBADENGINEThe package requires a Node.js (or npm) version that does not match the currently running version
- EBADPLATFORMThe package is not compatible with the current operating system or CPU architecture
- EJSONPARSEnpm could not parse a JSON file — typically package.json or package-lock.json
- ELIFECYCLEAn npm lifecycle script (preinstall install postinstall etc.) exited with a non-zero status code
- ENEEDAUTHThis operation requires authentication but no credentials were found
- ENOLOCKnpm requires a package-lock.json (or npm-shrinkwrap.json) but none was found
- ENOVERSIONSNo versions of the package satisfy the requested version range
- EOTPA one-time password is required to complete this operation
- EPEERINVALIDA peer dependency requirement could not be satisfied by the packages currently installed