package transfers: scoped package transfers are not supported
A scope is - by definition - ownership. We cannot transfer ownership of scoped packages.
Edward Thomson committed
Apr 5, 2021 at 17:12 UTC
6fd570a836cbc4a20840ab90322639d16aa77159
1 file changed
+2
-2
content/packages-and-modules/updating-and-managing-your-published-packages/transferring-a-package-from-a-user-account-to-another-user-account.mdx
+2
-2
@@ -2,13 +2,13 @@
2
title: Transferring a package from a user account to another user account
3
---
4
5
-As a package owner or maintainer, you can transfer ownership of a package you no longer wish to maintain to another trusted npm user on either the npm website or the command line.
5
+As a package owner or maintainer, you can transfer ownership of a package you no longer wish to maintain to another trusted npm user using either the npm website or the command line.
6
7
For more information on how npm support handles package name disputes between users, you can refer to npm's [package name dispute policy][dispute-policy].
8
9
<Note>
10
11
-**Note:** If your package is scoped and private, the new package owner must also have a [paid user account](https://www.npmjs.com/pricing). It is possible to transfer ownership of user-scoped packages, however we don't recommend it because it can create some ownership confusion.
11
+**Note:** You cannot transfer a scoped package to another user account or organization, because a package's scope _is_ the user account or organization name. You will need to create a new package in the new scope.
12
13
</Note>
14