Reading the source is a skill

When behavior surprises you, the dependency's source is right there in your node_modules / site-packages / vendored tree. Reading it is a muscle: start at the public function, follow the one path you care about, ignore everything else.

Half the time you find a comment that explains the exact edge case you hit. The other half you find the bug.