fix(deps): update dependency fast-equals to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
fast-equals	4.0.3 -> 5.2.2

---

Release Notes

planttheidea/fast-equals (fast-equals)

v5.2.2

Compare Source

• #​139 - Add file extensions to type definition files to allow it to work in projects with NodeNext module resolution

v5.2.1

Compare Source

Bugfixes

• #​138 - Actually fix reference to src code in index.d.ts by flattening types in file

v5.2.0

Compare Source

Enhancements

• Support Preact objects in equality comparison

Bugfixes

• #​137 - Fix circular React references in object comparisons

v5.1.3

Compare Source

Enhancements

• #​136 - More than double speed of iterables (Map / Set) equality comparisons

Maintenance

• #​135 - Include dequal and dequal/lite in benchmark comparisons

v5.1.2

Compare Source

Maintenance

Re-release of 5.1.0 with correct pre-release setup.

v5.1.1

Compare Source

DO NOT USE

This was an accidental pre-release when cleaning up release setup.

v5.1.0

Compare Source

Enhancements

• #​127 - Add support for custom Function instance comparisons (resolves #​118)
• #​128 - Add support for URL instance comparisons (resolves #​121)
• #​129 - Add support for Error instance comparisons (resolves #​123)
• #​130 - Add support for custom Number instance comparisons (resolves #​112)

Bugfixes

• #​132 - Fix assert.deepEqual check in benchmark (resolves #​125)
• #​126 - Export explicit types via export type (attempts to resolve #​114)

v5.0.1

Compare Source

Bugfixes

• Fix reference to metaOverride in typings and documentation (holdover from temporary API in v5 beta)

v5.0.0

Compare Source

Breaking changes

constructor equality now required

To align with other implementations common in the community, but also to be more functionally correct, the two objects being compared now must have equal constructors.

Map / Set comparisons no longer support IE11

In previous verisons, .forEach() was used to ensure that support for Symbol was not required, as IE11 did not have Symbol and therefore both Map and Set did not have iterator-based methods such as .values() or .entries(). Since IE11 is no longer a supported browser, and support for those methods is present in all browsers and Node for quite a while, the comparison has moved to use these methods. This results in a ~20% performance increase.

createCustomEqual contract has changed

To better facilitate strict comparisons, but also to allow for meta use separate from caching, the contract for createCustomEqual has changed. See the README documentation for more details, but froma high-level:

• meta is no longer passed through to equality comparators, but rather a general state object which contains meta
• cache now also lives on the state object, which allows for use of the meta property separate from but in parallel with the circular cache
• equals is now on state, which prevents the need to pass through the separate isEqual method for the equality comparator

createCustomCircularEqual has been removed

You can create a custom circular equality comparator through createCustomEqual now by providing circular: true to the options.

Custom meta values are no longer passed at callsite

To use meta properties for comparisons, they must be returned in a createState method.

Deep links have changed

If you were deep-linking into a specific asset type (ESM / CJS / UMD), they have changed location.

NOTE: You may no longer need to deep-link, as the build resolution has improved.

Enhancements

New "strict" comparators available

The following new comparators are available:

• strictDeepEqual
• strictShallowEqual
• strictCircularDeepEqual
• strictCircularShallowEqual

This will perform the same comparisons as their non-strict counterparts, but will verify additional properties (non-enumerable properties on objects, keyed objects on Array / Map / Set) and that the descriptors for the properties align.

TypedArray support

Support for comparing all typed array values is now supported, and you can provide a custom comparator via the new areTypedArraysEqual option in the createCustomEqual configuration.

Better build system resolution

The library now leverages the exports property in the package.json to provide builds specific to your method of consumption (ESM / CommonJS / UMD). There is still a minified UMD version available if you want to use it instead.

arePrimitiveWrappersEqual option added to createCustomEqual configuration

If you want a custom comparator for primitive wrappers (new Boolean() / new Number() / new String()) it is now available.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.