No description provided.
What's the difficulty level of implementing this one? (Or what are the files to look at/pseudocode? :))
Well, it would be simple to add a field to smart.json that indicated "last version of meteor tested with", which was prominently displayed on the package page.
The next challenge would be to get package authors to actually use it, which would probably require meteorite looking at it when deciding if a package can be installed.
Yeah. So it's one part smart.json field, one part wtf page update?
And one part updating the package page, yeah
+1 currently packages are in an unknown & incompatible state with certain meteor versions