chore(deps): update dependency chai to v5.3.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
chai (source)	5.2.0 -> 5.3.3
@types/chai (source)	5.0.1 -> 5.2.3

---

Release Notes

chaijs/chai (chai)

v5.3.3

Compare Source

What's Changed

• fix: keep names in bundle by @​43081j in #​1702
• chore: support publishing v5 by @​43081j in #​1703
• chore: update npm tag name by @​43081j in #​1704

Full Changelog: chaijs/chai@v5.3.2...v5.3.3

v5.3.2

Compare Source

Reverts the removal of the bundled version of chai in 5.3.1

What's Changed

• Update core contributors by @​keithamus in #​1697
• feat: reintroduce bundle by @​43081j in #​1699

Full Changelog: chaijs/chai@v5.3.1...v5.3.2

v5.3.1

Compare Source

What's Changed

• chore: remove bundled chai by @​43081j in #​1694

Full Changelog: chaijs/chai@v5.3.0...v5.3.1

v5.3.0

Compare Source

What's Changed

• chore: change main to point at chai directly by @​43081j in #​1696

Full Changelog: chaijs/chai@v5.2.2...v5.3.0

v5.2.2

Compare Source

What's Changed

• chore: use files for publishing by @​43081j in #​1695

Full Changelog: chaijs/chai@v5.2.1...v5.2.2

v5.2.1

Compare Source

What's Changed

Mostly internal changes but @​SuperchupuDev realised the package.json engines field was out of date, so it has been updated to reflect that v5.0.0 onwards only supports Node >=18.

• build(deps): bump serialize-javascript and mocha by @​dependabot in #​1673
• build(deps-dev): bump esbuild from 0.19.10 to 0.25.0 by @​dependabot in #​1671
• Enable no-var rule and fix violations by @​koddsson in #​1675
• Convert Assertion function to a class by @​koddsson in #​1677
• More typing by @​koddsson in #​1679
• build(deps-dev): bump tar-fs from 3.0.6 to 3.0.8 by @​dependabot in #​1682
• build(deps-dev): bump tar-fs from 3.0.8 to 3.0.9 by @​dependabot in #​1688
• chore: fix lint errors and add lint to CI by @​43081j in #​1689
• docs: update minimum node version in readme by @​SuperchupuDev in #​1691
• chore: update minimum node version by @​SuperchupuDev in #​1692

New Contributors

• @​SuperchupuDev made their first contribution in #​1691

Full Changelog: chaijs/chai@v5.2.0...v5.2.1

---

Configuration

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

🚦 Automerge: Enabled.

♻ 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 these updates again.

---

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

---

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @types/[email protected]
npm error Found: @types/[email protected]
npm error node_modules/@types/chai
npm error   dev @types/chai@"5.2.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @types/chai@"<5.2.0" from @types/[email protected]
npm error node_modules/@types/chai-subset
npm error   dev @types/chai-subset@"1.3.6" from the root project
npm error
npm error Conflicting peer dependency: @types/[email protected]
npm error node_modules/@types/chai
npm error   peer @types/chai@"<5.2.0" from @types/[email protected]
npm error   node_modules/@types/chai-subset
npm error     dev @types/chai-subset@"1.3.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-10-21T23_35_06_602Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-21T23_35_06_602Z-debug-0.log