All Projects → npm → feedback

npm / feedback

Licence: CC-BY-4.0 License
Public feedback discussions for npm

Labels

Projects that are alternatives of or similar to feedback

DNSSuffix
A set of PowerShell tools for managing the computer's primary DNS suffix.
Stars: ✭ 19 (-79.12%)
Mutual labels:  registry
DesktopAppLink
Creates hyperlinks to call desktop applications from
Stars: ✭ 15 (-83.52%)
Mutual labels:  registry
singularityhub.github.io
Container tools for scientific computing! Docs at https://singularityhub.github.io/singularityhub-docs
Stars: ✭ 68 (-25.27%)
Mutual labels:  registry
crux.land
crux.land is a free registry service meant for hosting small (≤ 20kB) single deno scripts.
Stars: ✭ 50 (-45.05%)
Mutual labels:  registry
qucli
Manage repositories in Quay.io
Stars: ✭ 29 (-68.13%)
Mutual labels:  registry
registry
Joomla Framework Registry Package
Stars: ✭ 16 (-82.42%)
Mutual labels:  registry
registry
TLD Management Software
Stars: ✭ 32 (-64.84%)
Mutual labels:  registry
nnrm
🔧 New nrm (NPM registry manager). Use smaller dependencies.
Stars: ✭ 55 (-39.56%)
Mutual labels:  registry
modelforge
Python library to share machine learning models easily and reliably.
Stars: ✭ 18 (-80.22%)
Mutual labels:  registry
cleanreg
A small tool to clean up Docker Registries (v2).
Stars: ✭ 48 (-47.25%)
Mutual labels:  registry
schema-registry
📙 json & avro http schema registry backed by Kafka
Stars: ✭ 23 (-74.73%)
Mutual labels:  registry
openshift-disconnected-operators
No description or website provided.
Stars: ✭ 52 (-42.86%)
Mutual labels:  registry
iox-registry
No description or website provided.
Stars: ✭ 23 (-74.73%)
Mutual labels:  registry
sregistry
server for storage and management of singularity images
Stars: ✭ 96 (+5.49%)
Mutual labels:  registry
WindowsRegistry
Windows Registry Tweaks & Hacks
Stars: ✭ 31 (-65.93%)
Mutual labels:  registry
cli
Autocode CLI and standard library tooling
Stars: ✭ 3,791 (+4065.93%)
Mutual labels:  registry
sack.vfs
Node addon which adds a virtual file system interface; websockets; json(6) parsing; sql support(sqlite,odbc); javascript sched_yield; ssl certificate generation; more...
Stars: ✭ 29 (-68.13%)
Mutual labels:  registry
ttl.sh
An anonymous & ephemeral Docker image registry
Stars: ✭ 107 (+17.58%)
Mutual labels:  registry
unit-converter
Convert standard units from one to another with this easy to use, lightweight package
Stars: ✭ 104 (+14.29%)
Mutual labels:  registry
inspr
Inspr is an agnostic application mesh for simpler, faster, and securer development of distributed applications (dApps).
Stars: ✭ 49 (-46.15%)
Mutual labels:  registry

npm public feedback discussions

In this repository, you can find the official npm public feedback discussions for every part of npm including the cli, documentation, the registry, and the website.

These discussions are where you can share suggestions for how the products should be improved and discuss those improvements with the community, including members of the npm product team. Check out Making Suggestions to learn how to provide feedback.

This feedback process is heavily influenced by the official GitHub public feedback discussions. Thank you to the team who worked on that for paving the path!

Making suggestions

We encourage you to open a discussion if you have suggestions for how we can improve npm. You don't need to have a solution to the problem you are facing to kick off a discussion. We are hoping to foster productive and collaborative conversations, so please check out how to give good feedback if you want some guidance on how to kick off a successful discussion.

Prior to making a new discussion please take a look at previous discussions to see if someone else has already brought to our attention your suggestions. If you find a similar discussion reply with additional details or react to signal your support rather than creating a new discussion.

From a suggestion to a shipped feature

Once you kick off a discussion, the npm team will do our best to make an initial response within 14 days. From there, we will work with you (and the entire community) to ensure we understand the current capabilities npm is missing and explore the space for potential solutions to your problem statement:

  • If the npm team determines that we are going to prioritize a feature to solve the problem that you've identified, we will mark the discussion as answered and update it periodically on the progress of the feature.
  • If the npm team determines not to pursue the problem that you have identified, we will mark the discussion as answered and will respond with our reasoning so our decisions can remain transparent.

npm CLI changes and the RFC (Request for Comment) process

The majority of feature requests for changes to the npm CLI will be directed towards the npm CLI RFC process. Often it may make sense to simply open a RRFC rather than a discussion in this repostiory.

Disclaimer

Any statement in this repository that is not purely historical is considered a forward-looking statement. Forward-looking statements included in this repository are based on information available to GitHub as of the date they are made, and GitHub assumes no obligation to update any forward-looking statements. The forward-looking comments in the public feedback discussions do not represent a commitment, guarantee, obligation or promise to deliver any product or feature, or to deliver any product and feature by any particular date, and is intended to outline the general development plans. Customers should not rely on these public feedback discussions to make any purchasing decision.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].