; Date: Thu Feb 13 2020
request package has been in the Node.js community since the beginning. It provides excellent comprehensive support for making HTTP requests from inside a Node.js application. However....
These stats tell us a lot, that it is an extremely popular package. It also says it is a large package, and that there's a lot of outstanding issues and pull requests.
Back in May 2019, Mikeal Rogers (the creator of Request and many other packages), posted an issue to the Request Github repository suggesting that the team should Deprecate Request rather than try to patch it up for the modern era. See: https://github.com/request/request/issues/3142
As Mikeal noted - in 2009 when he created Request, it used API's that predate the standard Callback paradigm, the Streams paradigm, the existence of
node_modules, the npm package manager, and of course newfangled features like async/await, classes, Promises, and all the rest.
The Request team did migrate the internals to some of the new features. But in his estimation, redeveloping Request to use the new features would entail a complete rewrite.
Therefore it is Mikeal's opinion that:
The most valuable thing
The best thing for these new modules is for request to slowly fade away, eventually becoming just another memory of that legacy stack. Taking the position request has now and leveraging it for a bigger share of the next generation of developers would be a disservice to those developers as it would drive them away from better modules that don’t have the burden of request’s history.
It does not mean that Request will stop making releases. But any new release will be very minor in scope, probably limited to critical bug fixes.
In the comments we see that Request has effectively been in this status for some time. The large number of outstanding issues and pull requests, for example, suggests that the Request team had slowed putting effort into the package.
Another issue lists a number of alternative packages: https://github.com/request/request/issues/3143