Update dependency @joist/di to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@joist/di	1.8.6 -> 4.3.0

---

Release Notes

joist-framework/joist (@​joist/di)

v4.3.0

Compare Source

v4.2.4

Compare Source

v4.2.3

Compare Source

v4.2.2

Compare Source

v4.2.1

Compare Source

v4.2.0

Compare Source

v4.1.1

Compare Source

v4.1.0

Compare Source

v4.0.1

Compare Source

v4.0.0

Compare Source

v3.9.2

Compare Source

v3.9.1

Compare Source

v3.9.0

Compare Source

v3.8.0

Compare Source

v3.7.0

Compare Source

v3.6.0

Compare Source

v3.5.0

Compare Source

v3.4.0

Compare Source

v3.3.0

Compare Source

v3.2.1

Compare Source

v3.2.0

Compare Source

v3.1.3

Compare Source

v3.1.2

Compare Source

v3.1.1

Compare Source

v3.1.0

Compare Source

v3.0.7

Compare Source

v3.0.6

Compare Source

v3.0.5

Compare Source

v3.0.4

Compare Source

v3.0.3

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source

v1.8.10

Compare Source

v1.8.9

Compare Source

v1.8.8

Compare Source

v1.8.7

Compare Source

---

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.

[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: @joist/[email protected]
npm ERR! Found: @joist/[email protected]
npm ERR! node_modules/@joist/di
npm ERR!   @joist/di@"3.1.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @joist/di@"^1.0.0" from @joist/[email protected]
npm ERR! node_modules/@joist/component
npm ERR!   @joist/component@"1.8.6" from the root project
npm ERR!   peer @joist/component@"^1.0.0" from @joist/[email protected]
npm ERR!   node_modules/@joist/router
npm ERR!     @joist/router@"1.8.6" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @joist/[email protected]
npm ERR! node_modules/@joist/di
npm ERR!   peer @joist/di@"^1.0.0" from @joist/[email protected]
npm ERR!   node_modules/@joist/component
npm ERR!     @joist/component@"1.8.6" from the root project
npm ERR!     peer @joist/component@"^1.0.0" from @joist/[email protected]
npm ERR!     node_modules/@joist/router
npm ERR!       @joist/router@"1.8.6" 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-03-12T17_00_12_201Z-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: @joist/[email protected]
npm ERR! Found: @joist/[email protected]
npm ERR! node_modules/@joist/di
npm ERR!   @joist/di@"4.3.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @joist/di@"^1.0.0" from @joist/[email protected]
npm ERR! node_modules/@joist/component
npm ERR!   @joist/component@"1.8.6" from the root project
npm ERR!   peer @joist/component@"^1.0.0" from @joist/[email protected]
npm ERR!   node_modules/@joist/router
npm ERR!     @joist/router@"1.8.6" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @joist/[email protected]
npm ERR! node_modules/@joist/di
npm ERR!   peer @joist/di@"^1.0.0" from @joist/[email protected]
npm ERR!   node_modules/@joist/component
npm ERR!     @joist/component@"1.8.6" from the root project
npm ERR!     peer @joist/component@"^1.0.0" from @joist/[email protected]
npm ERR!     node_modules/@joist/router
npm ERR!       @joist/router@"1.8.6" 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/2025-11-18T14_59_12_303Z-debug-0.log