npm error codes

16 codes — tap one for its meaning, causes, and fix steps.

• 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
• EPUBLISHCONFLICTThe package version you are trying to publish already exists in the registry
• ERESOLVEnpm could not resolve the dependency tree — a package requires a version that conflicts with what another package requires
• ETARGETNo matching version found for the specifier — the target version or tag does not exist
• EUSAGEAn npm command was invoked with invalid arguments or an unrecognized combination of flags