Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The worst offender, IMO, is request. I've seen more than a few projects pull it in just to make a single HTTP call. Just look at its package.json:

https://github.com/request/request/blob/master/package.json



I'd argue the offending party is the library pulling in Request for making a few simple HTTP calls.

Request itself in my opinion is a great piece of work, it does pretty much anything one would want to do with an HTTP client.


Yes, the npm "request" module is extremely bloated and badly written, to boot. https://www.npmjs.com/package/needle is a good alternative.


Can you elaborate? How do I know Needle is any better?


Why not just use node-fetch? It's tiny.


Could you elaborate on why you view this list of dependencies as a problem?

I've been using request and its many transitive dependencies for years without hitting any real problems due to this.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: