Package registry not found?

[newgoogledrive]

Select Topic Area

Bug

Body

(this is not feedback idk why it shows up as feedback) So, I'm still kinda new to GitHub and don't know much computer talk (like suepr advanced things at least). Anyway, I have been trying to publish a GitHub package and literally every time I test it out it says that it couldn't find it in the registry. Which makes sense because it's a GitHub package for npm. But GitHub is recommending me this code, and I don't know how to make it work. Here is the package: https://github.com/newgoogledrive/SqueakJS-embed-kit/pkgs/npm/squeakjs-embed-kit (I'm in GitHub codespaces by the way)

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams.
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences.
• GitHub staff may reach out for further clarification or insight.
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Mayureshju]

Yeah, this error happens a lot when using GitHub’s npm registry for the first time. The “package not found” message usually just means that npm is still looking at the public npmjs.com registry, not GitHub’s registry.

Here’s the setup you need for GitHub Packages (npm):

✅ 1. Create or update your .npmrc file

Make a file named .npmrc in your project and add:

@newgoogledrive:registry=https://npm.pkg.github.com 

Make sure @newgoogledrive matches your GitHub username exactly.

---

✅ 2. Log in to GitHub’s npm registry

Run this inside your Codespace:

npm login --registry=https://npm.pkg.github.com 

When it asks:

• Username: your GitHub username
• Password: a GitHub PAT with read:packages + write:packages
• Email: anything works

---

✅ 3. Make sure your package name is scoped in package.json

Your package.json should look like:

{"name": "@newgoogledrive/squeakjs-embed-kit", ... }

If the package name is not scoped, GitHub won’t link it to your registry.

---

✅ 4. Publish your package

npm publish 

---

After this…

You should be able to install it with:

npm install @newgoogledrive/squeakjs-embed-kit 

If anything still breaks, feel free to share your package.json here and I can check if the scope matches correctly.

[ComplianceOne]

yes

[newgoogledrive]

I do have a question, does the .npmrc file go in the root of the repo?

[newgoogledrive]

Also, is it fine if the PAT is classic? I think that’s the only type that can read and write packages.

[newgoogledrive]

I have a problem, your step 2 doesn't work at the passowrd portion. I'm trying to type in my PAT (classic) and it keeps saying access denied. I'm not sure what I'm doing wrong.

[newgoogledrive]

Thank you so much, I’ll try that now.