filter-obj

At the moment, non-enumerable properties are removed from the return value. On one hand: Most functional utilities iterate on objects using standard , , etc. which ignore non-enumerable properties. Object spreading itself removes non-enumerable properties. The concept of a property being non-enumerable implies that it should not be iterated when being copied over. Non-enumerable properties are much less common on plain objects than on class instances, and this library is meant for plain objects. On the other hand, some users might not expect non-enumerable properties removal as a side effect of this library. For example: : this would remove if it is non-enumerable, even though the user operation only intended to exclude . : this would not include if it is non-enumerable, even though the user explicitly requested to include it. For predicate functions, the user intent is less clear. @sindresorhus What are your thoughts on this?

Similar to #34, this uses a distributive conditional type that returns the correct type when using on a union type. I'm not sure if there is a strange edge-case that means this does not work as-expected for , I don't want to break types for regular use.