Publish your own library on NPM

One 、 register npm account number

Address ：https://www.npmjs.com/signup

Two 、 Log in at the command line npm account number

View the current npm Is the warehouse address https://registry.npmjs.org/ , If not, you need to modify the address

#  View the current  npm  Warehouse address 
npm config get registry

At present npm The warehouse address is not https://registry.npmjs.org/ To modify

#  modify  npm  Warehouse address 
npm config set registry https://registry.npmjs.org/

Sign in npm Warehouse

npm login

enter one user name 、 password 、 mailbox 、 One time password （ Get through email ） Login after

3、 ... and 、 Release

The command line under the package to be published is as follows ：

Initialize project

npm init

Release

npm publish

Go to the official website to check your packages And then there is

Four 、 Common mistakes

1、 Package name Already exists

npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/xxx - Package name too similar to existing package xxx; try renaming your package to 'xxx' and publishing with 'npm publish --access=public' instead
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy.

2、 Naming problem （ There are uppercase letters in the package name ）

npm ERR! code E400
npm ERR! 400 Bad Request - PUT https://registry.npmjs.org/xxx - "xxx" is invalid for new packages

3、 Duplicate version

npm ERR! code E403
npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/xxx - You cannot publish over the previously published versions: 1.0.0.
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy.