package fail to be published

[helmuthdu]

🏷️ Discussion Type

Bug

Body

Hello,

I'm trying to publish a new package called @vielzeug/arsenal, I have a monorepo and I have successfully published 30 other packages but this one no matter what always return 404. The package seems to have been created but never published, and it can be confirmed by the command curl -s https://registry.npmjs.org/@vielzeug%2farsenal.

Could you help me to fix this issue?

PS: contact support form always return an error loading page when trying to submit a request.

Thank you in advance.

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

[TheBoneJarmer]

Today I tried publishing a newer version of a package that exists on npm for years, also a 404. Now, I know they changed the authentication a lot at NPM and now I need to use 2FA in order to authenticate and publish my package. The alternative are granular tokens but they have a maximum expiration of 90 days.

I modified the .npmrc file located in my home folder and removed my old token (which expired like two months ago). This forced the npm cli to ask for authentication in the browser using 2FA instead. After providing the one-time access token I re-ran npm publish and got it published.

But man, what a mess. I feel really bad for the folks who automated this in a build step.

[rohanbyale]

This appears to be a legitimate bug rather than a usage issue.

Since your other packages publish successfully from the same monorepo, but "@vielzeug/arsenal" consistently returns a 404 despite the package seemingly existing in the registry metadata, it suggests the publish process may have failed on the registry side or left the package in an inconsistent state.

The failed support form is also concerning, as registry-related issues often require intervention from the npm support team. If possible, include:

• The exact "npm publish" command.
• The full error output (with verbose logs).
• Your npm and Node.js versions.
• Whether the package name was previously published or reserved.

This information will help the npm maintainers investigate the registry issue more efficiently.