Is this project still active?

[uliromahn]

I haven't seen any activity or commits for two years now. I am wondering if this project has been abandoned and should not be used?

Thanks!

[honestydeveloper]

Hi Uli. Can we have a chatting on Skype for discussing the project? my skype is live:.cid.9a6b56a0cc7c1897 Best Regards, Khoa.

[backnight]

I'm greatly interested about the status of the project. We use it in a lot of applications so we may be open to allocate internal resources to maintain it if necessary.

Thanks a lot.

[SSANSH]

+1

[kiennt23]

+1

[alanhe421]

If it is not maintained, are there any other options under node?

[karlbalagtey]

bump

[raaymax]

+1

[q0rban]

If it is not maintained, are there any other options under node?

I would check out fast-proxy or http2-proxy. fast-proxy with undici performed better than http2-proxy in my benchmarks, but the former does not support proxying websockets (that I could figure out), if that is a requirement for you.

I've also got my 👁️ on fastify/fast-proxy#40, in case any work is done to merge these two modules.

[traviswimer]

@q0rban I think I trust http-proxy a little more, simply because it still has 13 million downloads a week.

It's been over a year since either of the projects you mentioned have been updated, so I don't think they are actively maintained either. They also aren't nearly as widely used as this one.

None of the choices are ideal, but I think I'm going to stick with this one for now.

[q0rban]

I guess it depends on what your goals are for your implementation. In our case, performance, modern JS, and active (reputable) maintenance are important.

fast-proxy is maintained by Fastify and has commits from them as recent as 3 weeks ago.

node-http-proxy hasn't been touched in almost 3 years and the majority of the work on it is from 9+ years ago. https://github.com/http-party/node-http-proxy/graphs/code-frequency

It also has quite a few performance bottlenecks.

[traviswimer]

has commits from them as recent as 3 weeks ago.

Interesting. I wonder why they haven't updated the npm package in a year. Maybe they're in the process of reviving the project?

[alanhe421]

maybe we should fork and maintain by ourselves. just rename the npm package name.

[traviswimer]

@alanhg This comes to mind: https://xkcd.com/927/

[re-thc]

has commits from them as recent as 3 weeks ago.

Interesting. I wonder why they haven't updated the npm package in a year. Maybe they're in the process of reviving the project?

I thought they've moved to work on @fastify/http-proxy instead.