The breaking news landed a few days ago, with a simple commit entitled "doc: note full deprecation".
As of writing, over 40K packages rely on
request. In fact, it's the 4th most depended upon package on npm. And it has a whopping 18.5 million weekly downloads.
For the most familiar with the package's development, there's no news here.
request was in maintenance mode since March 2019 (see issue #3142). And deprecating the package is just one step further.
Without paraphrasing too much @mikeal statement back from March 2019, here are the key points that led to this deprecation:
- Back in 2009,
requestwas one of the first modules ever created for the Node.js ecosystem.
- For a few years,
requestand Node.js evolved together, each learning from the other.
- And as one of the very first modules listed on npm,
requestquickly became one of the most downloaded.
"The place request has in the Node.js ecosystem is no longer one of an innovator but of an incumbent." @mikeal
That's right that most tutorials, even here on DEV, use
request as the per-default HTTP client - while there are dozens of very good alternatives.
"The best thing for these new modules is for
requestto slowly fade away, eventually becoming just another memory of that legacy stack." @mikeal
That's the very first time that I see such a humble position. It's truly clever. And while it's going to require 40K+ packages to be upgraded, that's totally worth it.
What do you think?