Http/2 Still not working?

[GaryMatthews]

When are we going to see real progress on http2 support out of the box? we literally have thousands of scripts that depend on express and still not able to move to nodes http2 module. i've looked into the master, 5.0 and 5.x branches but there seams to be very few pushes into those repos to fix current backwards compatibility problems, firing up test server to check them and make incremental changes only to find ten other issues is getting frustrating. ALL these issues and errors go back a couple of years. due to the time and investment in express the only way forward at this time is to fork the stable branch and move on with a our own compatibility layer and then incrementally remove express from our workflow.

New issue created because it is frustrating reading through "issues" that date back years on this and see no real progress in the area of supporting the node built in http2 module.

log.txt

[dougwilson]

Hi @GaryMatthews it seems you already know this is a duplicate of existing issues, especially the main tracking issue of #2761

If you're looking to ask about the current state, it is best to ask in one of those issues, as it will actually send a notice to the users who are / have been involved with the work. if it is not moving at the pace you're looking for, you're always welcome to contribute or other work towards it, or potentially even funds to the folks who are working on it.

If you have other suggestions in order to help move it forward, I'm sure others will be very interested, and posting in the existing issues will be sure to notify the relevant individuals vs a new issue in which many of those folks will not be getting your message from.

[wesleytodd]

Hi @GaryMatthews, this is an Open Source library maintained by volunteers. The people who opened the http2 support issues did not follow through. If you would like to champion this, you are welcome to join the discussions the TC has had and take it from there. I am going to close this issue because it is not productive, but if you would like to get involved and help move http2 support forward feel free to message here and I can point you in the right direction.

[wesleytodd]

Oh, Hi @dougwilson. Posted at the same time!

[dougwilson]

And to be clear also: we're not closing this issue because we don't care; but leaving it open doesn't particularly accomplish making the code appear, unfortinately. If you want to get involved as @wesleytodd noted above, we'd be happy to bring you in to whatever would be relevant to get you onboard contributing code towards the feature you're wanting 👍

[wesleytodd]

Also, I need to start sending people to this to get the word out! Here is the new StatusBoard which shows what the TC top priorities and other issues we want people to get involved in. If you feel like the whole http2 conversation is too large of a topic to start on you can also take a look at the help wanted and discussion tags.

https://expressjs.github.io/statusboard/

[GaryMatthews]

noted.

[martixy]

While this is a duplicate, this issue isn't useless - it offers a clear, concise, and (as of this comment) up to date answer to the question to anyone googling their way around the issue. It is also the only resource I found which links to the status board above.