This topic is intended for discussing maybe a year or two down the road when atom has a stable package set and the excitement of developing new packages has died down a little bit.
package.json or similar.
Another situation would be if a package developer suddenly goes silent and no work is being done on an “official” repo, but a fork exists with more features and is actively being developed. How can users of the “dead” package learn of the newer, better supported one? In this case, marking packages as “deprecated” would have to come from the community (and could lead to issues should a developer come back and find their package no longer recognized as “official”)
Does atom provide a facet to manage these situations?
I’m not even sure if this is a major problem that should even be addressed, but I have personally experience similar issues using community extended programs (like Firefox, etc) where I’d go months or even years without knowing development for an outdated or incompatible addon was picked up by another developer.
Thanks for your time, all.