What needs to happen for express 5 to go beta?

[xjamundx]

What needs to happen for express 5 to go beta or even to be fully released?

At this point I see @dougwilson sending people to the upgrade guide in some of the issues.

How can we help get this over the line. my hunch is that many many people are doing dangerous things with async functions not realizing that they need https://www.npmjs.com/package/express-async-errors.

How can I help?

[dougwilson]

The best method is to work to provide code and docs for the issues listed at the top of the 5.0 PR. We are actually working on the last remaining things in the router repo currently.

At this moment I am recovering from sickness but otherwise getting out a 4.x release with a security fix, then spending time working on the last remaining 5.0 stuff as fast as I can.

Duplicate of #4728

[xjamundx]

For reference this is the PR I think you're referring to: #2237

I can help with docs or whatever. I did a whole egghead course about using express 5 already 😂

[dougwilson]

Yep, exactly. I would normally even offer if you like a Zoom or similar conversion to talk over to get you started on something you could help, but I have currently cronic cough and unable to really speak at the moment 😞

[xjamundx]

I'm so sorry Doug. Is there a way to DM you with more questions. Totally fine if the answer is not at the moment.

[dougwilson]

Yea, we can do that. Give me like 30 mins to just finish getting some food and then if you like we can DM in Gitter (just uses Github) or you can email me and we can find another medium like a Discord server or something if that works better.

I just want to get 5.0 out before the end of the year like mad anymore. Any help would be great as there are just a bunch of random loose ends all over that just need the final push, lol. Constant dumb security reports have been such a drain as they target popular projects with bogus reports I have to spend fighting off, otherwise next thing you know there will be a CVE issued that makes no sense and is unfixable.

[seniloper]

The best method is to work to provide code and docs for the issues listed at the top of the 5.0 PR. We are actually working on the last remaining things in the router repo currently.

At this moment I am recovering from sickness but otherwise getting out a 4.x release with a security fix, then spending time working on the last remaining 5.0 stuff as fast as I can.

Duplicate of #4728

You should get well soon
The battle with nextjs intensified
exprressjs needs help ;)