Incorrect usage of assert.deepStrictEqual in benchmark script

[Nevro]

If values are equal assert.deepStrictEqual return is undefined witch is converted to falsy return.

 const packages = {
   'assert.deepStrictEqual': (a, b) => {
     try {
-      return assertDeepStrictEqual(a, b);
-    } catch (e) {
+      return assertDeepStrictEqual(a, b) === undefined;
+    } catch {
       return false;
     }
   },

[planttheidea]

Has been resolved as-of 5.1.0.

[Nevro]

Deno:

error: Relative import path "assert" not prefixed with / or ./ or ../
  hint: If you want to use a built-in Node module, add a "node:" prefix (ex. "node:assert").
    at file:///storage/git/fast-equals/benchmark/index.js:3:58

[planttheidea]

@Nevro I created #140 from the post above, and fixed it with #141 .

In the future, rather than piggybacking on a closed issue, please create a new issue. I know both relate to usage of assert in benchmarks, but the problems related to assert were completely unrelated, and by having dedicated issue tracking it helps with visibility and resolution mapping.