We were getting some errors that I didn't really know how to fix, but
considering the warnings about them being outdated, and updating them
fixing it, it does seem like this was the right call.
Frivolous dependencies are bad for perf and bad for security.
The usual justification for frivolous dependencies is something like
"a community-maintained package is more likely to be bug-free and
maintained than something you wrote yourself", but:
1. frivolous dependencies are usually maintained by Just Some Random
Guy, not by some community
2. you are probably more likely to introduce a bug using some guy's API
incorrectly, than by writing a few lines of raw JavaScript that you
understand inside and out
3. if that guy deprecates his package, or decides to ragequit, or
whatever, you do not want to be depending on it
4. debugging becomes a lot more annoying
5. the dependency is full of unnecessary complexity to support use
cases we're not even using
Anyway, yeah, there's no need for this dependency.
