-
Notifications
You must be signed in to change notification settings - Fork 419
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
Deprecate/archive and recommend peggy.js as official successor project? #675
Comments
As far as we can tell, there is nobody who has the keys to this repo or to http://pegjs.org that is willing to do anything, or that even still responds to messages. Several people have tried multiple times. I don't think there's much more we can do at this point, other than respond to folks who ask questions here and direct them to Peggy. |
Fair enough, I guess anyone who starts using pegjs for anything substantial is bound to land somewhere that mentions peggyjs at some point. |
@lionel-rowe Thanks for posting this! I was shocked to find pegjs.org hosting a garbage "domain auction" site; I might not have found peggy.js without this issue. I'm swapping my dependencies now. |
Maybe it is possible to inform npm that |
As of 2024-03-16, https://pegjs.org no longer hosts content related to the PEG.js project -- see https://web.archive.org/web/20240316193229/https://pegjs.org/ * pegjs/pegjs#639 * pegjs/pegjs#675
As of 2024-03-16, https://pegjs.org no longer hosts content related to the PEG.js project -- see https://web.archive.org/web/20240316193229/https://pegjs.org/ * pegjs/pegjs#639 * pegjs/pegjs#675
As this project is basically dead (last commit 4 years ago) and peggy.js is the de-facto successor (3 commits in the last few days), it would make sense to make it official, deprecate/archive this repo, and add a link in the README pointing to peggyjs/peggy. Any reason not to do that, other than the maintainer not being active on GitHub any more?
The text was updated successfully, but these errors were encountered: