Mix public NPM registry with GitHub Packages with the same scope / namespace

[theshortcut]

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?

[amankr1469]

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.
For example, create subnamespaces like "@yourorg/public/package-name" and "@yourorg/private/package-name" for individual packages.

[theshortcut]

npm doesn't allow subnamespacing as far as I can tell. going more than 1 level deep results in something like:

npm ERR! Invalid name: "@scopename/subscope/packagename"

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[musadiqpeerzada-refyne]

Was there a solution for this?

[mrlubos]

@musadiqpeerzada-refyne @theshortcut If you're still struggling with this, I created a proxy that handles both npm and GitHub Packages https://npm.pkg.heyapi.dev/

Configuring it is straightforward in your .npmrc

//npm.pkg.heyapi.dev/:_authToken=${TOKEN}
@hey-api:registry=https://npm.pkg.heyapi.dev

Assuming you're publishing private packages to GitHub Packages, TOKEN would be the GitHub personal access token. Contact me if you need some changes to it!