Mix public NPM registry with GitHub Packages with the same scope / namespace #106941
Unanswered
theshortcut
asked this question in
Npm
Replies: 1 comment 1 reply
-
I guess public NPM registry and GitHub Packages private packages sharing the same scope with the same org name can definitely lead to conflicts and confusion. But you can utilize subnamespaces within your existing org scope. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Question
Body
We are running into issues trying to use packages published from our org to the public NPM registry and GitHub Packages registry private packages. Both sets of packages use the same
@scope
being owned by the same org name.Does GitHub packages allow for publishing under a different namespace or anything else that could simplify this setup?
Beta Was this translation helpful? Give feedback.
All reactions