Indicate supported Meter versions on Atmosphere

[StorytellerCZ]

With Meter 3.0 nearing there will be a lot of outdated packages. It is critical that when searching through Atmosphere (and Packosphere @copleykj ) that supported Meteor versions are displayed in the information so that developers know if they can install that package for their Meteor version.

The versionsFrom can be a good initial indicator to help determine the supported version range. I would also like to suggest that any packages that pre-date Meteor 1.3 (as in versionsFrom and last update) should be automatically marked as deprecated.

This will require a bit more thought as different version of packages support different version so a more advance feature might be needed.

I will also look into adding a description on how to choose proper versionsFrom for a package into the guide.

[Grubba27]

Noted! will add this to my backlog so this is implemented in Atmosphere

[zodern]

This would be very helpful. It could show the oldest and newest Meteor version each package supports. It would be nice if it could do it per package version, so apps on older Meteor versions could see which versions of a package it could use (though Meteor should install the correct version when adding the package).

The versionFrom isn't included when publishing a package. It's just a more convenient way to set the constraints of each core package, and a number of packages do that manually instead; the published package is the same either way. Atmosphere would need to check the constraints from any core packages, and then figure out which Meteor releases those constraints would be compatible with.

I would also like to suggest that any packages that pre-date Meteor 1.3 (as in versionsFrom and last update) should be automatically marked as deprecated.

There are packages from before Meteor 1.3 that should still work with Meteor 3 without modifications, like zodern:nice-reload. The constraints check should still work correctly for these.