dhei/classic-tokens
@reggi/path-to-regexp
dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2
dependabot/npm_and_yarn/main/eslint-10.4.0
dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0
dependabot/npm_and_yarn/main/proc-log-7.0.0
dependabot/npm_and_yarn/npm_and_yarn-826852524d
dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2
deprecate-totp-2fa
dhei/classic-tokens
gat-bypass-2fa-docs
jpg619/fix-accessibility-content-flow
jpg619/version-bump-tar-2
kartykp/gat-bypass-2fa-docs
kartykp/upgrade-path-to-regex
main
maitxn/version-bump-tar
patch-1
reggi/cache-based-on-version
reggi/dev-engines
reggi/fix-transform-prettier
reggi/overrides
update-search-sensitivity
| 1 | --- |
| 2 | title: npm-owner |
| 3 | section: 1 |
| 4 | description: Manage package owners |
| 5 | github_repo: npm/cli |
| 6 | github_branch: release/v10 |
| 7 | github_path: docs/lib/content/commands/npm-owner.md |
| 8 | redirect_from: |
| 9 | - /cli-documentation/v10/cli-commands/npm-owner |
| 10 | - /cli-documentation/v10/cli-commands/owner |
| 11 | - /cli-documentation/v10/commands/npm-owner |
| 12 | - /cli-documentation/v10/commands/owner |
| 13 | - /cli-documentation/v10/npm-owner |
| 14 | - /cli-documentation/v10/owner |
| 15 | - /cli/v10/cli-commands/npm-owner |
| 16 | - /cli/v10/cli-commands/owner |
| 17 | - /cli/v10/commands/owner |
| 18 | - /cli/v10/npm-owner |
| 19 | - /cli/v10/owner |
| 20 | --- |
| 21 | |
| 22 | ### Synopsis |
| 23 | |
| 24 | ```bash |
| 25 | npm owner add <user> <package-spec> |
| 26 | npm owner rm <user> <package-spec> |
| 27 | npm owner ls <package-spec> |
| 28 | |
| 29 | alias: author |
| 30 | ``` |
| 31 | |
| 32 | ### Description |
| 33 | |
| 34 | Manage ownership of published packages. |
| 35 | |
| 36 | - ls: List all the users who have access to modify a package and push new versions. Handy when you need to know who to bug for help. |
| 37 | - add: Add a new user as a maintainer of a package. This user is enabled to modify metadata, publish new versions, and add other owners. |
| 38 | - rm: Remove a user from the package owner list. This immediately revokes their privileges. |
| 39 | |
| 40 | Note that 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. |
| 41 | |
| 42 | If you have two-factor authentication enabled with `auth-and-writes` (see [`npm-profile`](/cli/v10/commands/npm-profile)) then you'll need to go through a second factor flow when changing ownership or include an otp on the command line with `--otp`. |
| 43 | |
| 44 | ### Configuration |
| 45 | |
| 46 | #### `registry` |
| 47 | |
| 48 | - Default: "https://registry.npmjs.org/" |
| 49 | - Type: URL |
| 50 | |
| 51 | The base URL of the npm registry. |
| 52 | |
| 53 | #### `otp` |
| 54 | |
| 55 | - Default: null |
| 56 | - Type: null or String |
| 57 | |
| 58 | This is a one-time password from a two-factor authenticator. It's needed when publishing or changing package permissions with `npm access`. |
| 59 | |
| 60 | If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. |
| 61 | |
| 62 | #### `workspace` |
| 63 | |
| 64 | - Default: |
| 65 | - Type: String (can be set multiple times) |
| 66 | |
| 67 | Enable running a command in the context of the configured workspaces of the current project while filtering by running only the workspaces defined by this configuration option. |
| 68 | |
| 69 | Valid values for the `workspace` config are either: |
| 70 | |
| 71 | - Workspace names |
| 72 | - Path to a workspace directory |
| 73 | - Path to a parent workspace directory (will result in selecting all workspaces within that folder) |
| 74 | |
| 75 | When set for the `npm init` command, this may be set to the folder of a workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project. |
| 76 | |
| 77 | This value is not exported to the environment for child processes. |
| 78 | |
| 79 | #### `workspaces` |
| 80 | |
| 81 | - Default: null |
| 82 | - Type: null or Boolean |
| 83 | |
| 84 | Set to true to run the command in the context of **all** configured workspaces. |
| 85 | |
| 86 | Explicitly setting this to false will cause commands like `install` to ignore workspaces altogether. When not set explicitly: |
| 87 | |
| 88 | - Commands that operate on the `node_modules` tree (install, update, etc.) will link workspaces into the `node_modules` folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, _unless_ one or more workspaces are specified in the `workspace` config. |
| 89 | |
| 90 | This value is not exported to the environment for child processes. |
| 91 | |
| 92 | ### See Also |
| 93 | |
| 94 | - [package spec](/cli/v10/using-npm/package-spec) |
| 95 | - [npm profile](/cli/v10/commands/npm-profile) |
| 96 | - [npm publish](/cli/v10/commands/npm-publish) |
| 97 | - [npm registry](/cli/v10/using-npm/registry) |
| 98 | - [npm adduser](/cli/v10/commands/npm-adduser) |