chore(deps): update dependency chai to v4.5.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
chai (source)	4.3.10 -> 4.5.0

---

Release Notes

chaijs/chai (chai)

v4.5.0

Compare Source

v4.4.1

Compare Source

What's Changed

• fix: removes ?? for node compat by @​43081j in https://github.com/chaijs/chai/pull/1574

Full Changelog: chaijs/chai@v4.4.0...v4.4.1

v4.4.0

Compare Source

What's Changed

• Allow deepEqual fonction to be configured globally (4.x.x branch) by @​forty in https://github.com/chaijs/chai/pull/1553

Full Changelog: chaijs/chai@v4.3.10...v4.4.0

---

Configuration

📅 Schedule: Branch creation - "* 0-4 * * 3" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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.

[github-actions]

[puLL-Merge] - chaijs/[email protected]

logError The patch is trivial, no need for a summarization

[github-actions]

[puLL-Merge] - chaijs/[email protected]

Description

This PR introduces a new configuration option deepEqual to customize the deep equality comparison function used in assertions. It also updates the type-detect dependency and makes several internal changes to use the custom deepEqual function where appropriate.

Changes

Changes

1. chai.js:

   • Added a new flag eql to the Assertion constructor, which contains the deepEqual function to be used.
   • Updated various assertions to use the new eql flag instead of directly calling _.eql.

2. lib/chai/config.js:

   • Added a new configuration option deepEqual to allow users to specify a custom deep equality comparison function.

3. lib/chai/core/assertions.js:

   • Updated multiple assertions to use the new eql flag instead of _.eql.
   • Modified the keys assertion to use the custom eql function for deep comparisons.

4. package.json:

   • Updated the version to 4.5.0.
   • Updated the type-detect dependency to version 4.1.0.

5. test/configuration.js:

   • Added a new test case for the deepEqual configuration option.

Possible Issues

1. The introduction of a custom deepEqual function might lead to inconsistent behavior across different parts of the codebase if not implemented carefully.
2. Users who rely on the specific behavior of the current deep equality comparison might face unexpected results if they don't update their tests accordingly.

Security Hotspots

No significant security issues are apparent in this change. However, allowing users to provide custom comparison functions always carries a small risk of introducing vulnerabilities if not used carefully.