Help with GitHub packages

[newgoogledrive]

Select Topic Area

Bug

Body

So, as I stated in my last post, I couldn't figure out why I kept getting errors and the package kept saying the package was not found in the registry. I read the comments, fixed some code from the official documentation too, and the only comment so far is not really helpful. It said to use this command:

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

So I tried it and it asked for my username, password, and email. The post said to put a PAT with read:packages and write:packages (which I already have) into the password place. Every time, it kept giving me an error. And earlier when I somehow got it to work, when I typed my email in the email box it THEN said the same error. I don't know what's going on, I just want to publish a GitHub package. I have an .npmrc file, scoped, but it just doesn't work. Here's the other discussion from earlier: https://github.com/orgs/community/discussions/180869 And here's the repository that has the package: https://github.com/newgoogledrive/SqueakJS-embed-kit P.S. I've been using GitHub Codespaces.

Edit: I think I found the problem. I was using GitHub actions, which is not as good for publishing packages. The problem isn't that the package isn't publishing, it just doesn't have the right permissions on the PAT!!! I forgot about the read:packages permission!!!

[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. ⭐