Closed tomek-he-him closed 8 years ago
... I wonder if the dash in your username has something to do with this..
Mine does not have a dash and I have the same error
You should open a new issue on npm/registry
and link to this one, because this problem is something happening within the registry infrastructure. We've seen it a couple times recently, and I think the @npm/registry-team should be able to get it sorted out pretty quickly.
@tomekwi I believe you may just have to login again. The error message is not very good for this case. I tested everything and it seems to work as long as you are using a valid token.
@soldair I just tried it again after npm add-user
, and it did have an effect. Now my error message is You need a paid account to perform this action.
I started the issue listed above as a result.
If anyone else tries this, don't forget --access=public
after re-logging in, or when attempting to publish a new package, as that appears to be the cause of the referenced issue
because i believe this issue is resolved for @tomekwi. and a different issue is resolved @shinymayhem. I'm going to close this issue.
If anyone else has an issue like this that is unaddressed please email support@npmjs.com or comment on https://github.com/npm/registry/issues/2
Hi, very sorry I didn’t reply earlier – it’s quite a crazy time for me lately.
It did work, the problem was actually between the chair and the monitor. I was logged in as tomekwi
but not as parametric-svg
. Thank you for your patience and wonderful support!
By the way, perhaps if you made the error message more accurate than
npm ERR! 404 Not found : @parametric-svg/spec
npm ERR! 404
npm ERR! 404 '@parametric-svg/spec' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
…, I’d realize my mistake myself and not bother you here. Just a thought.
Thanks again!
like @tomekwi said... if you need to upload a scoped package (assume @thescopedpackage/test ) then you need to login (adduser) as 'thescopedpackage'.
for example this is what i did...
`npm adduser username:thenameofscope password: email(public): foo@example.com
npm login --scope=thescopename npm --access=public publish `
@mofc3t15 You are my hero!
The culprit for me was not having the user that is publishing the package in a org team (https://www.npmjs.com/org/myOrgNameHere/teams) within the organization. I had 0 teams in my org to be more precise, then I created a team, added the user that is publishing the package and it works now.
I have used the following commands to make it work:
npm login --scope=myOrgNameHere
npm publish --access=public
Hello,
I’m having problems publishing the scoped package
@parametric-svg/spec
(and any other@parametric-svg/…
). I don’t recall running into this before (I last published one of these in December) and I definitely don’t run into this when publishing non-scoped packages.Here are the steps which led to the problem and what npm complains:
Since you’ve asked for the contents of
npm-debug.log
, here they are: