You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
are-we-there-yet has been marked as deprecated though I am not sure about an alternative.
Impact:
Weekly downloads: 19,170,924 (npm)
Used by ~9.5 million repositories (Github)
Used by 441 packages (Github)
Maybe more of a general question: Should this project keep track of deprecated projects? In a sense this is already provided by npm through deprecation messages but they don't always offer alternatives. Also the tooling could be better:
npm only shows deprecation warnings during installation
since it is a somewhat unique package that doesn't have any obvious alternatives, it probably doesn't belong here (yet)
if we introduce a deprecated manifest at some point, maybe it'd fit there. though im not sure what the "suggestion" would be to the user other than "don't use it"
if someone finds or creates a battle tested alternative, maybe then we could add it
are-we-there-yet
has been marked as deprecated though I am not sure about an alternative.Impact:
Maybe more of a general question: Should this project keep track of deprecated projects? In a sense this is already provided by npm through deprecation messages but they don't always offer alternatives. Also the tooling could be better:
npm
only shows deprecation warnings during installationnpm outdated
does not show deprecated projectsnpm-deprecated-check
did not work for me due to some undefined errorThe text was updated successfully, but these errors were encountered: