chore(deps): update dependency @hapi/hapi to v21

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@hapi/hapi (source)	20.2.1 → 21.4.9

---

Release Notes

hapijs/hapi (@​hapi/hapi)

v21.4.9

Compare Source

v21.4.8

Compare Source

v21.4.7

Compare Source

v21.4.6

Compare Source

v21.4.5

Compare Source

v21.4.4

Compare Source

v21.4.3

Compare Source

v21.4.2

Compare Source

v21.4.1

Compare Source

v21.4.0

Compare Source

v21.3.12

Compare Source

v21.3.11

Compare Source

v21.3.10

Compare Source

v21.3.9

Compare Source

v21.3.8

Compare Source

v21.3.7

Compare Source

v21.3.6

Compare Source

v21.3.5

Compare Source

v21.3.4

Compare Source

v21.3.3

Compare Source

v21.3.2

Compare Source

v21.3.1

Compare Source

v21.3.0: 20.3.0

Compare Source

⚠️ This release contains security fixes, for more information see #​4425.

v21.2.2

Compare Source

v21.2.1

Compare Source

v21.2.0

Compare Source

v21.1.0

Compare Source

v21.0.0

Compare Source

Release notes: #​4386

hapi v21.0.0 is a medium-sized release focused on modernization and miscellaneous API improvements. All modules in the hapi.js ecosystem have been updated to officially support Node.js v18, be compatible with ESM projects, and drop support for Node.js v12. Plugins in the hapi.js ecosystem now support hapi v20+.

v20.3.0

Compare Source

v20.2.2

Compare Source

---

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 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: stylelint-config-recess-order@3.0.0
npm ERR! Found: stylelint@13.13.1
npm ERR! node_modules/stylelint
npm ERR!   dev stylelint@"13.13.1" from the root project
npm ERR!   peer stylelint@"11.x - 14.x" from stylelint-config-css-modules@2.3.0
npm ERR!   node_modules/stylelint-config-css-modules
npm ERR!     dev stylelint-config-css-modules@"2.3.0" from the root project
npm ERR!   2 more (stylelint-config-recommended, stylelint-config-standard)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer stylelint@">=14" from stylelint-config-recess-order@3.0.0
npm ERR! node_modules/stylelint-config-recess-order
npm ERR!   dev stylelint-config-recess-order@"3.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: stylelint@16.3.1
npm ERR! node_modules/stylelint
npm ERR!   peer stylelint@">=14" from stylelint-config-recess-order@3.0.0
npm ERR!   node_modules/stylelint-config-recess-order
npm ERR!     dev stylelint-config-recess-order@"3.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-09T15_11_17_289Z-debug-0.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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: stylelint-config-recess-order@3.0.0
npm ERR! Found: stylelint@13.13.1
npm ERR! node_modules/stylelint
npm ERR!   dev stylelint@"13.13.1" from the root project
npm ERR!   peer stylelint@"11.x - 14.x" from stylelint-config-css-modules@2.3.0
npm ERR!   node_modules/stylelint-config-css-modules
npm ERR!     dev stylelint-config-css-modules@"2.3.0" from the root project
npm ERR!   2 more (stylelint-config-recommended, stylelint-config-standard)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer stylelint@">=14" from stylelint-config-recess-order@3.0.0
npm ERR! node_modules/stylelint-config-recess-order
npm ERR!   dev stylelint-config-recess-order@"3.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: stylelint@17.11.0
npm ERR! node_modules/stylelint
npm ERR!   peer stylelint@">=14" from stylelint-config-recess-order@3.0.0
npm ERR!   node_modules/stylelint-config-recess-order
npm ERR!     dev stylelint-config-recess-order@"3.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-05-06T12_29_00_612Z-debug-0.log