How to publish your own NPM package

Preparation

• node Environmental Science , Please go to the official website to download
• npm account number , Please go to this link https://www.npmjs.com/signup register

Create project

perform npm init -y Initialize project

package.json file :

{
    
  "name": "demo",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "bin": {
    
    "demo": "index.js"
  },
  "scripts": {
    
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}

index.js file :
Be sure to add this line of code : #!/usr/bin/env node It means that node Running code in environment

#!/usr/bin/env node

console.log(' test !!!');

Local testing :

First step : Publish to global under the current release package directory node_modules
npm link
Go to test and input yourself directly package.json Inside bin Configuration commands , What I have here demo
The result is :

The second step : The global release package is associated under the local test project directory
npm link publishname

Disassociate :

It is necessary to test this movie locally . Mainly, canceling the association relationship can reduce the problems such as dependence on development, failure to install and lag .

1. Cancel the association between the test project and the global
   In the test project execution npm unlink publishname
2. Cancel the association between the publishing project and the global
   Execute in the release package project npm unlink publishname

Publish online :

There are about two steps :
First step : Login account .
perform npm login , No, npm If you have a local account, you need to execute npm adduser Add local npm account number
If you log in here and report an error , Under execution npm config set registry https://registry.npmjs.org , Must be npmjs Source
The second step : Publish to npmjs Official website
perform npm publish

Be careful : If you report here 403 Error of , No permission to submit to this package warehouse , The reason is that the package name has been occupied , Then modify the name of the definition package , Need to be in package.json File modification name Field changes its name , Its name must be preceded by the function domain name @username/packagename This format is named , And username It can only be the current user , perform npm whoami You can view the current user name