4 ms·

Can anyone recommend a library with the same API as request? For those of us that would be under hardship to rewrite the node-request portions of large stable

Can anyone recommend a library with the same API as request? For those of us that would be under hardship to rewrite the node-request portions of large stable services, but also can't/shouldn't to have deprecated libraries?

lootsauce 7y ago
Not identical but I am considering got because of nice docs and solid streaming support https://github.com/sindresorhus/got#comparison https://github.com/sindresorhus/got#comparison
- deleted 7y ago
  [deleted]
Klathmon 7y ago
This is going to sound glib, but you can just keep using what you have now. If you take a look at [1], the maintainers of request aren't "deprecating" it in the sense that they won't touch it ever again. It really just means that there won't be any more active development on it, no new features or breaking changes will be accepted, and some housekeeping had to be done to allow it to accept security fixes without relying on one specific person to be around. The code will still work (and probably for quite a while), and security issues will still be addressed, it just won't be changing much if at all from now on. [1] https://github.com/request/request/issues/3142 https://github.com/request/request/issues/3142
- lootsauce 7y ago
  I totally agree with this approach, however it seems like a good idea to use alternatives for future work.
  - Klathmon 7y ago
    Agreed, but if you are looking for alternatives with an identical API, then it doesn't seem like a good idea anymore (at least to me). The main theme behind the depreciation of Request is that the API is old and doesn't really fit with the rest of the node ecosystem. Any other API-compatible library is going to have those same issues. So if you are going to start something new, but want to keep an identical interface, then you might as well just use Request.

4 ms·

Can anyone recommend a library with the same API as request? For those of us that would be under hardship to rewrite the node-request portions of large stable

by ruffrey 7y ago

lootsauce 7y ago
Not identical but I am considering got because of nice docs and solid streaming support https://github.com/sindresorhus/got#comparison https://github.com/sindresorhus/got#comparison
- deleted 7y ago
  [deleted]
Klathmon 7y ago
This is going to sound glib, but you can just keep using what you have now. If you take a look at [1], the maintainers of request aren't "deprecating" it in the sense that they won't touch it ever again. It really just means that there won't be any more active development on it, no new features or breaking changes will be accepted, and some housekeeping had to be done to allow it to accept security fixes without relying on one specific person to be around. The code will still work (and probably for quite a while), and security issues will still be addressed, it just won't be changing much if at all from now on. [1] https://github.com/request/request/issues/3142 https://github.com/request/request/issues/3142
- lootsauce 7y ago
  I totally agree with this approach, however it seems like a good idea to use alternatives for future work.
  - Klathmon 7y ago
    Agreed, but if you are looking for alternatives with an identical API, then it doesn't seem like a good idea anymore (at least to me). The main theme behind the depreciation of Request is that the API is old and doesn't really fit with the rest of the node ecosystem. Any other API-compatible library is going to have those same issues. So if you are going to start something new, but want to keep an identical interface, then you might as well just use Request.