chore(deps): update dependency dompurify to v3.4.10

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
dompurify	resolutions	patch	3.4.9 → 3.4.10

---

Release Notes

cure53/DOMPurify (dompurify)

v3.4.10: DOMPurify 3.4.10

Compare Source

• Refactored codebase for clarity: extracted the public type declarations into types.ts
• Decomposed the three largest sanitizer functions into focused helpers
• Removed duplicated defaults and dead branches, consolidated SAFE_FOR_TEMPLATES scrubbing into single shared path
• Improved per-node performance by hoisting the mXSS probe regexes and testing textContent before innerHTML
• Added a deterministic micro-benchmark harness (npm run bench) with a --compare mode
• Reduced CI cost by running the full three-engine browser suite once per PR
• Refreshed the demos/ folder so every demo runs again, and added a SVG-via-<img> demo
• Documented the bench and test:happydom scripts in the README
• Completed the Attack Classes & Bypass History wiki page
• Bumped several dependencies where possible

---

Configuration

📅 Schedule: (UTC)

• 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 this update again.

---

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

---

This PR has been generated by Mend Renovate.

[claude]

Patch dependency update generated by Renovate — bumps dompurify in docs/ from 3.4.9 to 3.4.10.

Scope: Only docs/package.json and docs/yarn.lock are touched. No .NET source, engine logic, tests, or snapshots are affected.

Change is correct: The yarn.lock entry (version, resolved URL, and integrity hash) is consistent with the package.json version pin.

Release notes look safe: The 3.4.10 changelog is purely a refactor/performance/housekeeping release — no breaking changes, no API surface changes. The mXSS probe hoisting and textContent-before-innerHTML optimisation are neutral-to-positive for a docs-site sanitisation use case.

Auto-merge is already enabled, which is appropriate for this category of patch. Nothing here warrants blocking.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}