Unclear feedback from `npm owner ls`

dideler commented 6 years ago

I'm opening this issue because:

[ ] npm is crashing.
[ ] npm is producing an incorrect install.
[x] npm is doing something I don't understand.
[x] npm is producing incorrect or undesirable behavior.
[ ] Other (see below for feature requests):

What's going wrong?

When I try to identify the owner(s) of certain packages, npm responds with "admin party!". I have no idea what this means.

Actual behaviour

$ npm owner ls jackal
admin party!

Expected behaviour

$ npm owner ls jackal
some_npm_user <email@example.com>

supporting information:

npm -v prints: 5.8.0
node -v prints: v8.11.1
npm config get registry prints: https://registry.npmjs.org/
Windows, OS X/macOS, or Linux?: Linux

Sgtpanda commented 6 years ago

I suspected this might be hardcoded into npm and it is.https://github.com/npm/npm/blob/d46015256941ddfff1463338e3e2f8f77624a1ff/lib/owner.js#L117-L125

It appears that admin party! is printed when the API returns either no maintainers or an empty list of maintainers.

I agree that this behaviour is quite confusing.

sdellis commented 6 years ago

How does one rectify this? I can clearly see in my npmjs.com profile that I'm the owner of my package. However, locally, there are no owners listed and I get the admin party! response.

dideler commented 6 years ago

There's a support email on the npm website you can use. I had a similar problem when switching an account to org, and they helped solve it. Keep in mind they probably get lots of support requests and their resources are limited (especially for non-paid support) so you may not get a response right away.

sdellis commented 6 years ago

Thank you @dideler ... that is exactly my experience: account to org.

npm / npm