GitHub Community
Enabling private github packages #24554
-
|
We are trying to create our first private git-hub package, but we get the following error: npm ERR! code EPRIVATE How do we enable private packages? I see from https://github.com/features/packages that it says “GitHub Packages is not available for private repos in legacy per-repository plans.” How do I determine if that applies to me? We have had a plan allowing private repositories for some time, but I don’t think it is “per-repository”, it’s based on our organization. Is there something else I need to do to enable private packages? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi @jeconneely, Thank you for being here! I’m sharing the reply from our support team as it might help someone in the same situation:
npm has a confusing definition of private packages. They are packages that should never be published anywhere (hence the error). What we mean by private packages is packages that are associated with a private repository. You will need a PAT with access to that repository and the
You should remove the |
Beta Was this translation helpful? Give feedback.
Hi @jeconneely,
Thank you for being here! I’m sharing the reply from our support team as it might help someone in the same situation:
npm has a confusing definition of private packages. They are packages that should never be published anywhere (hence the error).
What we mean by private packages is packages that are associated with a private repository. You will need a PAT with access to that repository and the
read:packagesscope in order to access themYou should remove the
privatefield and instead associate the package with a private repository.See: https://help.github.c…