NPM-OWNER(3)

πŸ“¦ version 1.2.1, in nixos 26.05, nixpkgs unstable

πŸ’– NAME πŸ’–

npm-owner β€” manage package owners, bestie. This is the npm-owner(3) manual page, and it's literally all about who gets to run the package owner situation. πŸ‘‘


✨ SYNOPSIS ✨

npm.commands.owner(args, callback)

That's the call signature, no cap. 🫢


πŸŽ€ DESCRIPTION πŸŽ€

Okay so the first element of the args parameter decides what action we're doing, and the rest of the elements depend on that action. The possible actions are below, with the parameter order in parentheses, exactly like the original:

  • ls (package) β€” lists every user who has access to modify a package and push new versions. Super handy when you need to know who to bug for help. πŸ’…
  • add (user, package) β€” adds a new user as a maintainer of a package. This user is enabled to modify metadata, publish new versions, and add other owners. Slay, new owner privileges unlocked. πŸ”₯
  • rm (user, package) β€” removes a user from the package owner list. This immediately revokes their privileges. Bye bestie, access gone. πŸ’€
Heads up: there is only one level of access. Either you can modify a package, or you can't. Future versions may contain more fine-grained access levels, but that is not implemented at this time. So yeah, it's giving one-tier access, periodt. 🌸

πŸ‘€ SEE ALSO πŸ‘€

  • npm apihelp publish
  • npm help 7 registry

mwah πŸ’‹ that's the whole page, bestie β€” source/manual NPM-OWNER(3), dated March 2017. Go forth and manage those owners with main character energy. πŸ¦‹βœ¨

πŸ“¦ where this page comes from