npm Blog (Archive)

The npm blog has been discontinued.

Updates from the npm team are now published on the GitHub Blog and the GitHub Changelog.


I am pleased to announce that npm is transitioning its public issue trackers from GitHub to a Discourse site at 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 and login with your GitHub account or create a 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 in the appropriate section.

What, exactly, is happening?

When is this happening?

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