npm RFCs
A public RFC process for proposing and discussing changes to the npm CLI and its supporting web services.
What is npm RFCs?
npm/rfcs is the official repository for the Request for Comments (RFC) process governing the npm CLI. It is a public forum where changes and new features for the npm package manager are proposed, discussed, and formally accepted or rejected. The process structures community input and team decision-making to guide the evolution of npm.
npm CLI contributors, maintainers, and users in the JavaScript ecosystem who want to propose significant changes or understand the direction of the npm project. It is also relevant for package manager developers interested in collaborative governance models.
It provides a transparent, standardized, and inclusive mechanism for shaping the future of a critical tool in the JavaScript ecosystem, ensuring changes are well-considered and community-vetted before implementation.
Overview
Public change requests/proposals & ideation
Use Cases
Best For
- Proposing a new feature or flag for the npm CLI
- Understanding the rationale behind upcoming changes to npm
- Contributing to the design of a major npm ecosystem change
- Learning about open-source governance and consensus models
- Following the development direction of the npm package manager
- Engaging in structured technical discussions with the npm team
Not Ideal For
- Developers needing immediate bug fixes or patches for npm, as the RFC process is for proposing changes, not rapid troubleshooting.
- Teams wanting to propose changes solely to the npm registry API without CLI involvement, since the scope is limited to CLI and supporting web services.
- Individuals seeking casual feedback on npm usage ideas without formal documentation, due to the structured and document-heavy RFC requirements.
- Projects requiring guaranteed implementation timelines, as ratification doesn't obligate the npm team to implement or provide schedules.
Pros & Cons
Pros
Provides a clear template and workflow for submitting proposals via pull requests, ensuring all necessary information is included for productive discussion, as outlined in the 'How do I create an RFC?' section.
Uses a rough consensus model that prioritizes open discussion and surfaces all objections, making the rationale behind decisions visible, as described in the 'Rough Consensus' philosophy.
Allows both npm collaborators and the wider community to participate in RFC review and feedback, fostering a collaborative environment, as stated in the 'How does review work?' section.
Encourages breaking down large features into smaller, testable building blocks, which helps in thorough consideration and reduces risk, as emphasized in the 'Iterate on Building Blocks' principle.
Cons
The iterative nature and requirement for thorough discussion can lead to delays, and implementation is deferred based on team priorities, not guaranteed, as noted in 'What happens after ratification?'.
Open office hours have been suspended indefinitely, reducing opportunities for real-time discussion and community interaction, as mentioned in the 'Open Office Hours' section.
Despite community input, ultimate ratification authority rests with the npm CLI team, which can lead to perceived top-down decision-making, as clarified in the 'Final Authority' section.
Frequently Asked Questions
Related Projects
React RFCsRFCs for changes to React
Vue RFCsRFCs for substantial changes / feature additions to Vue core
OTEPsSpecifications for OpenTelemetry
Compose SpecificationThe Compose specification
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.