NPM: 403 forbidden - PUT http://registry.npmjs.org/[package-name] - Forbidden

Question

I am trying to create npm vue component library. I have been working through all the steps but stuck at npm publish.

Please see the below error screenshot for which I am unable to find a solution on google after trying more than an hour(The error message is not that accurate IMHO or maybe I am not able to catch it).

For reference package.json

{
  "name": "@satyam/vue-components",
  "version": "0.1.0",
  "main": "./dist/satyam.common.js",
  "files": [
    "dist"
  ],
  "scripts": {
    "serve": "vue-cli-service serve",
    "build": "vue-cli-service build",
    "build-library": "vue-cli-service build --target lib --name satyam ./src/components/index.js",
    "test:unit": "vue-cli-service test:unit",
    "lint": "vue-cli-service lint"
  },
  "dependencies": {
    "core-js": "^3.6.4",
    "vue": "^2.6.11"
  },
  "devDependencies": {
    "@vue/cli-plugin-babel": "~4.3.0",
    "@vue/cli-plugin-eslint": "~4.3.0",
    "@vue/cli-plugin-unit-jest": "~4.3.0",
    "@vue/cli-service": "~4.3.0",
    "@vue/eslint-config-standard": "^5.1.2",
    "@vue/test-utils": "1.0.0-beta.31",
    "babel-eslint": "^10.1.0",
    "eslint": "^6.7.2",
    "eslint-plugin-import": "^2.20.2",
    "eslint-plugin-node": "^11.1.0",
    "eslint-plugin-promise": "^4.2.1",
    "eslint-plugin-standard": "^4.0.0",
    "eslint-plugin-vue": "^6.2.2",
    "node-sass": "^4.12.0",
    "sass-loader": "^8.0.2",
    "vue-template-compiler": "^2.6.11"
  }
}

After running npm audit

Any help will be appreciated :)

Satyam Pathak · Accepted Answer · 2021-03-16T08:45:14.363

25

Update: New user needs to confirm their account first

So after quite a few research and digging around, I found the real issue here.

It's probably documented somewhere very deep or in a light font, but I totally missed to find it.

Your package name should follow your npm username.

In my package.json name property is @satyam/vue-components where it should be @satyamninja/vue-components and that's it. I successfully published the package.

edited Mar 16 '21 at 08:45

answered May 06 '20 at 07:42

Satyam Pathak

6,612
3
25
52

1

For future folks. The 403 forbidden was possibly because the ORG Scope for @satyam was already taken. To make this clear, the `npm username` is not required to follow your package scope. – Adrian Kremer Nov 19 '20 at 09:42

Hefaz · Answer 2 · 2021-03-16T18:21:24.387

22

If you are a new user, please confirm your account first!

edited Mar 16 '21 at 18:21

answered Jan 01 '21 at 13:47

Hefaz

526
1
8
24

2

Thanks, this fixed my issue straight away. So simple – Second2None Jan 31 '21 at 06:16
I'm glad, I could help! – Hefaz Feb 05 '21 at 09:20
2

thanks... saved me some heartache. why doesn't npm tell you to confirm your account. the reason you are probably creating an account is to try and publish something. – masonCherry Feb 11 '21 at 01:07

score 9 · Answer 3 · edited Jan 27 '21 at 22:53

This post has helped me moving past the 403 error, however, after confirming my account over the email link they send and after login into NPM I tried one more time, then I got the following error:

402 Payment Required - PUT https://registry.npmjs.org/@jcarbajal79%2fsimplelib3 - You must sign up for private packages.

If you have the same problem is because the library is being published as private, I checked my package.json and test the following:

No property: "private":"...". - does not work Property set "private":"true" - does not work Property set "private":"false" - does not work

Turns out you have to publish it as public from the command line:

%> npm publish --access=public. - Works!.

Thanks a lot, this did it for me too! – Hubert Hilczer Feb 21 '21 at 20:49 — Hubert Hilczer, Feb 21 '21 at 20:49

score 4 · Answer 4 · answered Mar 23 '21 at 14:22

4

It sound like you are a new user. You need to confirm your account. Should have get email confirmation from npm site.

answered Mar 23 '21 at 14:22

Denise Ignatova

465
4
7

score 3 · Answer 5 · answered Nov 23 '20 at 12:02

I got this error once and I figured out how to fix it after some search. you are getting the 403 forbidden error because there is possibly another package published on NPM with the same name as the one you are trying to publish, you will have to change that to another name. to do so, you can go to your package.json and edit the name of the package.

score 1 · Answer 6 · answered Jan 17 '21 at 20:37

1

If the answers mentioned above not working for anyone then you need to check if your email is verified with the npm account or not, If it's not verified just do the verification and you will be able to publish without any issues.

answered Jan 17 '21 at 20:37

Santosh Jaiswal

46
6

score 1 · Answer 7 · answered Jul 15 '22 at 15:39

1

This also happens because the name you gave the component in the name attribute found in package.json already exists in npm, I recommend giving the component a different name that doesn't exist.

answered Jul 15 '22 at 15:39

marvinCalvo

46
4

score 0 · Answer 8 · answered Jan 09 '23 at 16:15

I had the same error and was able to resolve by logging into npmjs.com from the command line i.e.

npm login
Username: *******
Password:
Email: (this IS public) *******@***.***
npm notice Please check your email for a one-time password (OTP)
Enter one-time password: 49720564
Logged in as ******* on https://registry.npmjs.org/.

Running npm publish then succeeded and I could see my package in my account.

NPM: 403 forbidden - PUT http://registry.npmjs.org/[package-name] - Forbidden

8 Answers8