### Context This epic aggregates key improvements for the npm repository that are required to make the Package Registry a complete product. ### How were these issues chosen As the PM, I used several different sensing mechanisms to create this list: 1. Product backlog review to identify frequently requested and customer issues. 1. Review weekly triage reports and identify any ~"priority::2" or ~"priority::3" bugs. 1. Customer and team feedback. ### Which issues are not here Because I will likely review these epics with customers, I did not include any known security-related issues, so as not to risk displaying an issue title by accident during a meeting. ### How can you help? - If you are facing a bug or need a feature that is preventing you from using the npm repository feature, please comment and ping @trizzi to consider adding it to this epic. - Check out the parent epic https://gitlab.com/groups/gitlab-org/-/epics/2891, which details all of the work required to move the Package Registry to the `Complete` maturity. ## Owners * Team: [Package Registry](https://about.gitlab.com/handbook/engineering/development/ops/package/package-registry/) * Most appropriate slack channel to reach out to: `#g_package-registry` * Best individual to reach out to: @radbatnag * PM: @trizzi * EM: @crystalpoole