Help users identify the correct version of package to use
Problem to solve
As highlighted in the recent Package Data survey, one of the top reasons why users go the package registry is:
To look up which version of a package I should be using in my environment
Intended users
Some ideas
As a way to help combat this, could we:
-
On project creation, check if the user / group has any packages hosted within the package registry and ask the user if they want to automatically include the latest version (or pick a version)? This would potentially require knowing what type of project is being created, so we'd need to work around that.
-
On the packages list inside a group / project, add a button like:
Add package to project
- this would create an MR that modifies the target project's package file (e.g.package.json
) to include the selected package. -
Add a button somewhere inside the project pages to allow the same as above but in reverse (select a package to add). Maybe we could also show such a button when viewing a package file (i.e.
package.json
) inside the repository? -
On the packages list page, highlight newer releases in some manner. Maybe a tag, different background colour or a feed closer to the top of the page?