Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Request’s Past, Present and Future #3142
Before I go into the details and reasoning I’ll get straight to the point. The most valuable thing
Apologies in advance to the other committers on
The first version of
It’s much harder for new libraries accomplishing similar tasks to gain adoption because of the incumbent position
The patterns at the core of
There’s a transition happening now in the ecosystem to these patterns. How messy that will be is still up in the air and I’m not going to try and read the tea leafs and figure out what the future looks like in that regard. The question for
A version of
The best thing for these new modules is for
Here’s the plan.
Things we might do - please discuss and volunteer!
maybe the same logical reasoning should be applied to expressjs? for request we now have the new shiny got module, there is no re-write or true alternative to expressjs on the horizon.
express is great, but it is not really actively updated with new features these years