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.
The text was updated successfully, but these errors were encountered:
Things we might do - please discuss and volunteer!
We get the following error when using this action downstream in FM. Likely caused by running an old node version which throws deprecation warnings. ``` Step 6/8 : RUN npm install -g firebase-tools ---> Running in 192a53453432 npm WARN deprecated firstname.lastname@example.org: request has been deprecated, see request/request#3142 npm WARN deprecated email@example.com: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated firstname.lastname@example.org: this library is no longer supported /usr/local/bin/firebase -> /usr/local/lib/node_modules/firebase-tools/lib/bin/firebase.js ```
"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."
Seems like the creator has better things to do in life than keeping track on things and to update "request" effectively to the "modern pattern". Well... "request" is now history.