This repository has been archived by the owner on Nov 6, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Maintainer notice #522
Comments
bnoordhuis
added a commit
that referenced
this issue
Oct 2, 2020
I'm moving on and as the last (semi-)active maintainer, that means http-parser is now effectively unmaintained. Refs: #522 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
This was referenced Mar 24, 2021
This was referenced Sep 13, 2021
13 tasks
6 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm moving on and as the last (semi-)active maintainer, that means http-parser is now effectively unmaintained.
It's a stable project for a stable protocol and I don't expect many issues but you should take the above into account when evaluating whether http-parser is the right choice for you.
For new projects and projects looking to migrate, I recommend https://github.com/nodejs/llhttp. Similar API, feature parity, well maintained and in active use.
The text was updated successfully, but these errors were encountered: