fix: Objects without prototype are now properly stringified

[Lu-Ks]

Hey,

I recently discovered that I was using the same key for different object shapes. Upon further investigation, I realized that the object I was attempting to hash did not have prototypes. Following the package workflow, I found that all these objects are hashed using a fallback value <:unknonw>:unknown. These objects may still contain data despite not having prototypes.

Example :

import { hasher } from "node-object-hash";

const hashSortCoerce = hasher({
  sort: true,
  coerce: false,
  alg: "md5",
});

const obj0 = Object.create(null);
console.log(hashSortCoerce.hash(obj0)); // 9e6a14d0fc429751a97d11e74803128e

const obj1 = Object.create(null);
obj1.name = "something";
console.log(obj1); // { name: "something" }
console.log(hashSortCoerce.hash(obj1)); // 9e6a14d0fc429751a97d11e74803128e

const obj2 = Object.create(null);
obj2.name = "else";
console.log(obj2); // { name: "else" }
console.log(hashSortCoerce.hash(obj2)); // 9e6a14d0fc429751a97d11e74803128e

I resolved the issue on my end by wrapping the objects with prototypes, but I believe others might encounter the same problem, which is why I submitted this PR.

Thanks 😃

[SkeLLLa]

Thanks for PR. I guess I'll need to update those pipelines first, since they a outdated as hell :).

[github-actions]

🎉 This PR is included in version 3.1.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀