in version 3.1.3 of the library the following comparison returns `false` ```js equal({ a: undefined }, {}) ``` That's quite a surprise for me, but since there are test-cases for this case, I guess it works as expected. It would be good to have an option to ignore `undefined` values.