Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternative for are-we-there-yet #117

Open
filipre opened this issue Jul 26, 2024 · 1 comment
Open

Alternative for are-we-there-yet #117

filipre opened this issue Jul 26, 2024 · 1 comment

Comments

@filipre
Copy link

filipre commented Jul 26, 2024

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
  • npm outdated does not show deprecated projects
  • npm-deprecated-check did not work for me due to some undefined error
@43081j
Copy link
Contributor

43081j commented Jul 26, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants