We should check if this package is used on class instances in the wild, as this would break sorting them. Perhaps an alternative would be Object.keys(value).length !== 0. However, I agree your approach makes the most sense.

Hey, thank you for your feedback. I see, checked and understand your concern and I agree that it breaks class instances when sorting.

Object.keys(value).length !== 0 unfortunately also leaves pure JS objects (instead of class instances) if they have properties (X { y: 2 } -> { y: 2 }).

Hey @balupton, I've added additional handling for cases when there are class instances.

Please take a look and let me know if you see any issues ;)

Thanks again for your response!

• npm run our:compile ✅
• npm run our:test ✅

Hey @balupton any opinions on this one or should I close this PR? :)

Thanks!

Back to work from backpacking, give me a few weeks to catch up