Introducing the npm public roadmap and a new feedback process

npm opens up its planning with a public roadmap repo

GitHub’s npm team is making its product planning more visible to the JavaScript community. Following last week’s release of npm v7.0.0, the maintainers have launched two new public repositories: a roadmap for tracking upcoming work and a feedback channel for community-driven feature discussions.

The roadmap repo aims to show a complete picture of what the team is building across the CLI, documentation, registry, and website. A project board organizes items by stage and expected delivery timeframe, giving users a way to see what’s planned over the next few months rather than just what has already shipped.

The feedback repo complements the existing OpenRFC process for CLI proposals. Where RFCs focus on detailed technical specifications, the feedback discussions are intended for earlier-stage product ideas—problem statements without necessarily having a proposed solution. The npm product team will participate directly in these conversations.

How the feedback loop works

To suggest an improvement, users open a discussion in the feedback repo. The npm team aims to respond with an initial message within seven days. From there, the conversation moves toward understanding existing gaps and exploring possibilities.

The outcome is tracked publicly either way:

• If the team decides to pursue a feature addressing the problem, the work gets an issue on the public roadmap and is tracked there through development.
• If the team decides not to move forward, it opens an issue explaining the reasoning so the decision stays transparent.

For anyone unsure how to frame a request, the repo includes a guide on giving good feedback with advice on how to start a productive discussion.

The move extends the collaborative model that helped shape npm v7.0.0’s features to the rest of the platform, giving the community a clearer view of where the product is heading and why certain choices are made along the way.