3
JS projects can accumulate a ton of dependencies, but TIL that npm can explain why you have them. `npm explain foo` or `npm why foo` shows the dependency path to foo.
Super handy when you weren't expecting to depend on something.
miniblog.
Related Posts
It's incredibly hard to explain adversarial problems to users. I see gamers sincerely asking "why doesn't the publisher just fix the cheater problem?".
This is exacerbated by the fact that sharing too many details of anticheat can make the problem worse.
Using stack traces to explain type inference:
Nifty example of a Haskell lens library using custom type errors to explain what's wrong:
https://github.com/mrkgnao/silica/blob/master/README.md