The breaking news landed a few days ago, with a simple commit entitled "doc: note full deprecation".
That's right! request, one of the top and old...
For further actions, you may consider blocking this person and/or reporting abuse
Why not standard library anyways?
I really hate to see this error message in node-sqlite3. Why does need request, anyway?
You can use that if you want, but it is a little bit verbose to write compared to other libraries, which most developers don't like.
I kind of prefer the core HTTP module as well. It helps to really understand how it works in depth. But it's also pretty verbose compared to most frameworks/lib.
As I have mentioned in this StackOverflow answer, the reason for deprecation is both the interface and the underlying code.
Callbacks are very hard to deal with. This is why we have
promisifyandbindCallbackfor promises and observables, respectively. But, asrequestis a many-faced god, it's hard to get rid of its callback interface.I prefer a node fetch implementation in case I had a view for isomorphism, there is one less thing to change.
For pretty much everything I'm working on now, I cut off with fetch and async function support (around April 2017 and newer browsers). In node, I use node-fetch or setup a global if I'm sharing code libraries.
While fetch isn't perfect, usually create an api wrapper around it. It's standard, cleaner than alternatives and built into the browsers (smaller bundles).
That's exactly why @mikeal the creator of request deprecated the project
Yeah! fetch is easy to use and pretty well supported now.