This repository has been archived by the owner on Feb 2, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 30
Archiving this module / Do not use / New maintainer needed #91
Comments
+1 |
I prefer archiving over transferring out of the fastify org. |
This is a bummer, as we recently refactored our app to use this module after doing some benchmarks of this and other nodejs proxying modules. |
A willing maintainer is also an option. |
mcollina
changed the title
Archiving this module
Archiving this module / Do not use / New maintainer needed
Aug 8, 2023
Seems like no one is willing either, should we go ahead and archive the repo? |
FWIW, we ended up refactoring to fastify/http-proxy after hearing of plans to abandon this project. |
The module is deprecated on npm. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think we should be archiving this module, because it was born out of the will of @jkyberneees and myself to merge it and fastify-reply-from, creating a generic module for proxying in node.js.
However, such goals never materialized.
I would like to transfer this module back to @jkyberneees or archive this module if he is not interested in maintaining it anymore.
For some strange reasons I cannot add other people to do releases on this module, and I have no time to do them.
The text was updated successfully, but these errors were encountered: