…e doesn't bork the install of a new version.
Some packages don't have a "main" field, and they also have a lib folder with one file by the name of the package. Ie, something like this: .../foo/lib/foo.js So, after installing, you have to do require("foo/foo"). That's the require("foo/foo") problem. This fixes it by making it so that if you have to do require("foo/foo"), then require("foo") will give you the same thing.