Announcing npm.community

I am pleased to announce that npm is transitioning its public issue trackers from GitHub to a Discourse site at npm.community. This will allow us to give the community a single place to report bugs that impact npm, regardless if they’re on the website, in the command line tool or in the registry itself.

You can sign up today. Go to https://npm.community and login with your GitHub account or create a npm.community account.

What Will It Accomplish?

By changing from bug tracking software to forum software specifically designed for supporting software support we hope to better empower users to help other users, and to recognize their effort in doing so. This will also make it easier for teams within npm to work with the community to identify and resolve the issues that they’re encountering.

Discourse also gives is insight into what problems users are having the most often that GitHub issues do not. We will be producing regular reports on what we’re seeing and how that’s impacting our plans and priorities.

What About My Issues?

The existing repositories, including the one from the npm CLI will be archived. All existing issues will still be searchable, but further discussion will not be possible. If you want to discuss a previously existing issue, please copy it over to a new post on npm.community in the appropriate section.

What, exactly, is happening?

• npm/npm is being archived. Further issues, comments and PRs will no longer be possible.
  • Requests for help, diagnostics and other support questions go in the support category on npm.community.
  • Reports of bugs go in the bugs category on npm.community.
  • Feature requests go in the ideas category on npm.community.
  • New RFCs will still go in the npm/rfcs repo. Discussion of those RFCS goes in the RFCs category on npm.community.
  • Pull requests and releases will come from the new npm/cli repo.
• npm/registry is being archived. Further issues will no longer be possible.
  • Requests for help, diagnostics and other support questions go in the support category on npm.community.
  • Reports of bugs go in the bugs category on npm.community.
  • Feature requests go in the ideas category on npm.community.
• npm/www is being archived. Further issues will no longer be possible.
  • Requests for help, diagnostics and other support questions go in the support category on npm.community.
  • Reports of bugs go in the bugs category on npm.community.
  • Feature requests go in the ideas category on npm.community.
• npm/docs is being made private and reorganized.
  • npm/docs holds all the documentation on https://docs.npmjs.com except the “Using npm”, “CLI commands” and “Configuring npm” sections. Those sections will live in npm/cli.
  • Reports of bugs go in the bugs category on npm.community.

When is this happening?

You can join npm.community today! We plan to archive the repositories on the 12th or 13th of July, 2018. There will be another post here at that time.