I haven’t see any talk in the forums about the ‘request’ package going into deprecation: https://github.com/request/request, https://github.com/request/request/issues/3142
I don’t know if Meteor depends on the package to run, but I do know that the Meteor HTTP package depends on it. If it’s just the HTTP package, then it’s not really a big deal as developers can easily use better alternatives to ‘request’ directly from NPM.
From what I’ve read, ‘request’ will be in maintenance mode for 6 to 12 months before it’s basically abandoned.
Yes, I think there has been some talk about deprecating HTTP package as we already have the fetch package: https://atmospherejs.com/meteor/fetch
I think what we have to do now is to update the documentation.
Why not write http with fetch under the hood? Http is already in use in many apps and it is a great, dead-simple api to be used. At the same time it is written in a way, that replacing request with fetch should be of no problem here.
3 Likes
This should be an issue/update for the Meteor core team, right? I kind of agree with @jkuester on updating HTTP with fetch under the hood. It just seems like the right thing to do for everyone who uses HTTP in their apps, right?
Also just to clarify, the fetch package on Atmosphere is used internally to Meteor’s core and is basically a polyfill wrapper of node-fetch so it also works client-side?
I primarily use axios in my apps now (client & server), so this doesn’t seem like a big deal to me, but the community might be easily confused by this if HTTP is not updated or replaced with something else in the docs.
@filipenevola can you let us know if the Meteor core team has a plans for handling this?
1 Like