Name: registry
Owner: npm
Description: :package: :ledger: A public issue repo for the npm registry team.
Created: 2016-03-28 18:20:43.0
Updated: 2018-05-23 19:12:25.0
Pushed: 2018-03-06 21:37:37.0
Homepage: null
Size: 12523
Language: null
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
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.
If there are major releases going out, we will write them up here.
We will collect documentation about API endpoints here.
:white_check_mark: 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.
:white_check_mark: 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.
:warning: This team does not enforce policy. If you are interested in the policies of npm, please look at the policies repository.
:no_entry: This repository is not the place to bring package disputes. Contact support.
:no_entry: 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.
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.Participation in this repository (via issues, PRs, or otherwise) is subject to the npm Code of Conduct.