refactor: replace dequal w/ stable-hash

[SukkaW]

Continues from #85.

Unlike dequal, stable-hash uses shallow comparison and referential equality only (so mutable Object, Set, and Map won't have the same hash after mutation). And stable-hash outputs meaningful hash instead of version.

cc @kosmotema

[changeset-bot]

⚠️ No Changeset found

Latest commit: fa96904

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.23%. Comparing base (8b53954) to head (558378e).
Report is 7 commits behind head on master.

❗ Current head 558378e differs from pull request most recent head fa96904

Please upload reports for the commit fa96904 to get more accurate results.

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #99   +/-   ##
=======================================
  Coverage   96.22%   96.23%           
=======================================
  Files          91       91           
  Lines        4399     4410   +11     
  Branches     1497     1499    +2     
=======================================
+ Hits         4233     4244   +11     
  Misses        160      160           
  Partials        6        6           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kosmotema]

so mutable Object, Set, and Map won't have the same hash after mutation

Hm, it seems, that they will. Here is a small example:

import assert from "node:assert";
import stableHash from "stable-hash";

const foo = {};
const hash = stableHash(foo);
foo.bar = "baz";

assert.notStrictEqual(hash, stableHash(foo));

And stable-hash outputs meaningful hash instead of version

But do we really need a meaningful hash? Besides, this hash is not a real hash (since it's variable length, so it's more like a stringifier) and on some of our tests the full context hash can be up to 400 characters long. However, changing just one character would be enough to invalidate the previous ExportMap.

---

If you compare all the approaches, you get the following:

Point	JSON.stringify + hashify	dequal + version	stable-hash
Supports mutable objects	❌	❌	❌
Stability	🤔 (not always)	✅ (using deep equality)	✅ (using stable algorithm)
Hash length	fixed (64 chars)	varying (up to 16 chars)	varying (not limited by default)
Performance optimizations	❌	referential equality before deep compare	WeakMap for previously generated hashes
Simple implementation	❌	❌	✅ (we can just use stableHash instead of getOptionsVersion)

So we have three options:

• leave it "as is"
• use stable-hash and possibly have long hash strings, and replace getOptionsVersion with it (and also remove optionsVersionsCache completely)
• use stable-hash and then calculating real fixed-length hash (but this will be similar to the current approach)