Visual Representation of Outdated Dependency Versions

jchristman commented 9 years ago

For a package, it would be nice if the developer could see at a glance if his or her package depends on a package version that is out of date. That is, if twbs:bootstrap updates from 3.3.1_2 to 3.3.2 and my package uses 3.3.1_2, it would be useful if that were denoted somewhere on the package page, in a notification, etc. This would allow developers to make sure they are able to take full advantage of the features of someone's library.

Some ideas I have are:

Add a badge with the number of out-of-date dependencies to the package panel when viewing profile if the owner is logged in. Don't show it to everyone, just the owner. This would let the owner know at a glance which packages he or she needs to look at.
On a specific package's page, maybe make any out-of-date dependencies red?

domyen commented 9 years ago

Fantastic idea & suggestions @jchristman. Tracking this on the feature requests trello board.

cubitworx commented 9 years ago

I also think it would be really great to have the ability to include a dependency restriction in the search. For example when doing a search you could limit it to packages that are only compatible with Meteor > V1.0 - the filtered results would take into account all dependencies for that package.

As an example I recently tried to use LumaPictures/meteor-luma-ui with Meteor V1.1.0.2 and found that due to its dependency on mrt:iron-router-progress I couldn't use it since Meteor > V1 requires multiply:iron-router-progress instead... https://github.com/LumaPictures/meteor-luma-ui/issues/14

I have not created a new issue but instead have added my issue as a comment to this one since this is a relatively new request and both these issues relate to version dependency.

percolatestudio / atmosphere

Visual Representation of Outdated Dependency Versions #353