meta: ship 10 features and bug fixes created through public feedback

[MylesBorins]

Summary

In October of 2020 the npm team launched the new public feedback process. A primary goal is to improve transparency and give our community a voice in determining the roadmap of npm. Starting in Q3 of 2020 the npm team will prioritize and ship 10 different features and bug fixes that were discussed and prioritized based on the feedback process.

Intended Outcome

• Improvements to the CLI, Registry, and Website
• The npm team builds trust in our new feedback process
• The npm team is able to show how we prioritize work in a transparent fashion

How will it work

The community will engage in our discussions forum to make requests for changes to any of the npm products.

The npm team will respond and participate in discussion to help identify solutions to the problem statements identified in the discussion. The npm team will also host bi-weekly triage meetings to discuss the discussions at length.

Items that we choose to explore will be added to the future column of the roadmap. Once the requested item has been properly scoped it will be prioritized based on available engineering resources.

[MylesBorins]

We got a number of new features launched and bugs fixed through public feedback! We definitely got more than 10 done, but here are 10 of the things we did so we can exit green on this roadmap item 🎉

• website: show TypeScript information for packages that have type declarations
• website + registry: Use GitHub Flavored Markdown for README rendering
  • Broken assets path in README after Github flavoured markdown
  • Render README.txt as plain text, not as markdown
  • Render text READMEs in a monospace font
• registry: whoami endpoint for automation tokens
• website: sign out flow appears to not sign you out
• website: send fewer emails during sign up - and no marketing emails
• New docs site search bar performance
• cli: add set script command