npm Category Guidelines 🗃️

[grandmas-favorite]

Got thoughts about npm? The cli, documentation, the registry, etc? Here’s the place to chat! We welcome your feedback and conversations, so feel free to start a discussion!

✅ What is allowed in this category:

• Technical questions about npm, the cli, documentation, registry, etc.
• Product feedback requests
• Conversations and opinions on tooling/packaging

❌What is not allowed in this category:

• Discussions regarding GitHub Packages (will be recategorized)
• Posting job listings or contests
• Self-promoting your projects

If you post something that is not allowed, your post may be removed without notice and you may receive a temporary ban 🛑.

If you’re interested in learning more about this category, we’ve put together a FAQ below ❔. Have unanswered questions? Please let us know in the comments below.

[jerryTomson298]

It sounds like a great space for developers to discuss everything related to npm! The CLI, documentation, and registry are core parts of the JavaScript ecosystem, so having a dedicated place for feedback and discussion can be really helpful.

The inclusion of product feedback requests is a plus—it gives users a way to directly influence npm's development. However, the restrictions on self-promotion and off-topic discussions make sense to keep things focused.

One thing that could be interesting is how npm plans to engage with user feedback. Will the npm team be active in responding to issues, or is this more of a community-driven space? Also, how does it compare to discussions happening on GitHub Issues or other forums like Stack Overflow?

Have you participated in discussions there yet? I'd love to hear what kind of feedback people are sharing!

[rishadmohammad2007-ai]

It sounds like a great space for developers to discuss everything related to npm! The CLI, documentation, and registry are core parts of the JavaScript ecosystem, so having a dedicated place for feedback and
firebase_task_app.html
icon-zip-manager.tsx.txt
discussion can be really helpful.

The inclusion of product feedback requests is a plus—it gives users a way to directly influence npm's development. However, the restrictions on self-promotion and off-topic discussions make sense to keep things focused.

One thing that could be interesting is how npm plans to engage with user feedback. Will the npm team be active in responding to issues, or is this more of a community-driven space? Also, how does it compare to discussions happening on GitHub Issues or other forums like Stack Overflow?

Have you participated in discussions there yet? I'd love to hear what kind of feedback people are sharing!

[asma019]

Thanks for putting these guidelines together! 📝
It’s really helpful to have clear do’s ✅ and don’ts ❌ so discussions stay focused and productive. I like that the category is open to technical questions, product feedback, and deeper conversations about npm tooling — it encourages more collaborative problem-solving.

Also appreciate the clarity on what’s not allowed, especially around self-promotion and off-topic posts, since it keeps the space signal-heavy and spam-free.

Looking forward to contributing useful feedback and learning from others here! 🚀

[wolfletexed]

Hello npm Team,

I hope this message finds you well. As a developer who often works at night, I wanted to share a suggestion that I believe would greatly improve the user experience: adding a dark mode option to your website.

[amanmohdtp]

That's real. Like dark mode is really way more compatible.