-
Notifications
You must be signed in to change notification settings - Fork 45
Reevaluate dependencies #141
Comments
For All told, using |
if got is an alternative to request, how about needle? I very much liked what I saw when I looked at that. |
To follow up on this, EventEmitter3 should probably be replaced by the 'events' native module that it originally superseded. With correctly documented events the necessity for listening to all events in one listener and the usage of .once isn't substantial enough in my opinion. This would be a breaking change however, forcing an update to v6, not that that should stop it. |
+1 for using native |
The reason why Eventemitter3 is used is because of the performance improvements that it has over native events. The methods are the same as native events with major differences. All in all though, I don't see any of the dependencies we use ever being unpublished. That leftpad incident will not ever happen again as NPM has changed their policies to disallow that from happening. |
I like But, speaking of bufferutil, one of it's sub deps has a high security vulnerability
Current version of
|
and also current version: 5.0.2
it has also switched from |
PlugAPI seems to have a few deps that pull in a lot of other deps.
The worst ones in this regard are
bufferutil
andgot
.I would recommend looking at their usage and if they can be phased out.
I just made the move from
request
toneedle
and in our bot, and that was a lot of extra deps removed.Having a lot of dependencies is not an inherently good situation to be in, imo.
The text was updated successfully, but these errors were encountered: