I thought it was just a test package and wanted to remove it, but the NPM official doesn’t recommend this practice. In the process of trying, I released some packages. This form represents an individual, my-usernameThis corresponds to the user name in NPM. This form represents an organization, my-orgThe corresponding is the organization name in NPM. It should be noted that the package name in this form corresponds to the NPM account and cannot be filled in casually.
The other way is to specify parameters to indicate disclosure: npm publish -access public Therefore, the first way is to spend money to buy private package services.
View documents and find package name in this form is a package name with scope, which is executed npm publishThe default is to publish private packages. Error: 402 Payment RequiredĪfter changing the name and remembering the library I’ve seen, I imitated the package prefixed with and reported the following error when publishing it again:Įrror: 402 Payment Required – PUT – You must sign up for private packages Another way is to build your own services on the intranet.
NPM CONFIG SET REGISTRY BACK TO DEFAULT FREE
Because it is a free account, if you want to contract on NPM, you can either change the name or spend money to create a private package. Are you logged in as the correct user?Īfter searching the data, I found this issue, it turns out that there is already a library with the same name in the public library. After registering and logging in, prepare the library, and then execute npm publish, the following error is reported:Įrror: 403 Forbidden – PUT – You do not have permission to publish “xx”. Although I have published packages, I haven’t published my own package, so I refer to it npm developer guideI tried and got the following harvest.įollow the steps in the document.
0 kommentar(er)
