#Npm config set scope password#

Organization？？ Where was this created? Log in to NPM’s website, and really see the organization!!Ī new kaisaiui is built here. It means that every NPM package should have an organization as its namespace, so as to add package to it Thus it is also a good way to signal official packages for organizations. This means you don’t have to worry about someone taking your package name ahead of you. Why can’t I find it? Look at the official website of NPM again and find the following descriptionĮach npm user/organization has their own scope, and only you can add packages in your scope. Read the instructions on the official website, saying that access public should be added when publishing In step 3, if it is NPM publish, 403 will appear, as follows Step 1 and step 2 are the same as before.

Then in the root directory to be published.

#Npm config set scope password#

Log in to NPM (if you don’t have an account, you need to register first), and enter the user name, password and email.NPM distribution package Non scope package For example, packets under Vue are used by Vue, which is equivalent to a classification of packets.

In this way, the structure will be clearer after classification.

If it starts with then it is a scope package. That is to say, scope is equivalent to the namespace of NPM package. When used in package names, scopes are preceded by an symbol and followed by a slash, e.g. A scope follows the usual rules for package names (URL-safe characters, no leading dots or underscores). What does this mean? Check out the description on the official website of NPMĪll npm packages have a name. It was found that the package in node_modules has become Vue / cli XXX.