πŸ“¦ πŸ“’ A public issue repo for the npm registry team.
Latest commit caa8f18 Dec 6, 2016 @ashleygwilliams ashleygwilliams committed on GitHub Merge pull request #58 from npm/api-docs
public API docs
Permalink
Failed to load latest commit information.
docs Merge pull request #58 from npm/api-docs Dec 6, 2016
CONTRIBUTING.md add CONTRIBUTING.md Apr 5, 2016
README.md Updating chris to manager Jun 17, 2016

README.md

πŸ“¦ πŸ“’ the npm registry public tracker

This is a public issue tracker for the npm registry. It will be used to announce major changes, forecast what we are working on, and to field issues with the registry.

The registry team reports to @chrisdickinson.

The team members are:

What This Repo Is

If there are major releases going out, we will write them up here.

We will collect documentation about API endpoints here.

βœ… If you are having issues with the registry β€” a publish is too slow, or if you can't install a package you know exists β€” please open an issue here. If the topic is sensitive, please contact support.

βœ… If you need something from the registry β€” a new API, or new information in an existing API β€” please open an issue here. We will take the feature under consideration: keep in mind, we often have to pass on really good ideas due to time constraints. Wherever we can, we'll try to make your feature possible β€” if not written by us, then at least providing the hooks so that you can write it yourself.

⚠️ This team does not enforce policy. If you are interested in the policies of npm, please look at the policies repository.

⛔️ This repository is not the place to bring package disputes. Contact support.

⛔️ This repository is not the place to debate the outcome of package disputes. We rely on our support staff to administer the repository according to the policies set forth in the policies repository. If you wish to make changes to npm policy, please open an issue there.

What The Registry Team's Goals Are

  1. πŸ“¦ 🚚 The spice must flow. The registry must continue to distribute packages to folks running npm install. In so far as is possible, ensure that disruptions are avoided, and where unavoidable or unexpected, they are at least brief. One outcome of this rule is that making sure the service scales along with the ecosystem is always on our minds.
  2. πŸ’Š 🍡 Ensure the health of the ecosystem. This means making sure that bad actors are not able to adversely affect other users through their actions. (Put another way, it's our job to give all developers the elbow room they need to make sure they don't step on each others toes.)
  3. πŸ”¬ πŸš€ Develop features that help us keep running the registry. This includes both free features and for-pay features β€” sometimes this will involve working with the Enterprise team to develop public registry features that add value to the enterprise product, sometimes this will involve building features for private modules users.

Participation

Participation in this repository (via issues, PRs, or otherwise) is subject to the npm Code of Conduct.