📦 📒 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.
What The Registry Team's Goals Are
📦 🚚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.
💊 🍵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.) 🔬 🚀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 in this repository (via issues, PRs, or otherwise) is subject to the npm Code of Conduct.