Mark plugins supporting Hyper 2.x

[balazsorban44]

After updating Hyper to 2.0.4, most of the plugins stopped working. Would be nice to have it marked somehow if they will still work on the latest versions of Hyper or not.

[bnb]

Would love to be able to add this, not sure how we can reasonably go through all the plugins to test them. 🤔

[jrichard8]

Hyperpower and hyperline don't work anymore with hyper 2.x

[danieldelcore]

Should we just wait until v2 has launched and remove repos that don't upgrade or are no longer maintained after a certain amount of time? That way when you come to awesome-hyper you know that you can pickup anything and not have to worry about compatibility, operating systems, etc.

Maintaining version support for all of these repos will be impractical and i doubt that we'll get it right anyway.

[danieldelcore]

Obviously we should try to reach out to repository maintainers when their project falls behind and give them a chance to upgrade.

I'm also mindful that there isn't much out there regarding documentation of the new API and migration path. I'm hoping that Zeit and the Hyper community will surface docs to help us once the latest API is established and stable. Perhaps we could even reference that information somewhere here.

[balazsorban44]

Would it be possible to show the last updated date of a plugin repository in the README.md then? In a new column, right next to the downloads for example.
Please check out #304

[legowerewolf]

I think a really simple way would to add another column to the lists that indicates the last known version of Hyper that the extension works on. Add a message that "if you try one of these and it works, update the last-working-version to whatever you're on right now."

[SarcevicAntonio]

this is a great idea and relevant again with hyper 3.0 breaking plugins again...

[legowerewolf]

Use a field in the package json, saying what version range of Hyper is supported. Then Hyper can check that before applying the plug-in.