Authentication Required for Installing Public GitHub-NPM Package from Private Repository #121067
Replies: 1 comment
-
🕒 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 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 Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Authentication Required for Installing Public GitHub-NPM Package from Private Repository
Question
Have created a private repository on GitHub and published a public github-npm package from this repository. However, when trying to install the public package using npm, it prompts me for authentication. Is there a way to allow installation of the public package without authentication, considering that the package is published from a private repository?
I have followed the recommended steps for publishing the package. However, the authentication requirement persists, which is unexpected since the package itself is public.
Can anyone provide guidance on resolving this issue or clarify if authentication is mandatory even for public packages published from private repositories? I would appreciate any insights or workarounds to allow seamless installation of the public package without the need for authentication.
Beta Was this translation helpful? Give feedback.
All reactions