chore(deps): update dependency nodemon to v3.1.10

[renovate]

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

---

This PR contains the following updates:

Package	Change	Age	Confidence
nodemon (source)	3.1.4 -> 3.1.10

---

Release Notes

remy/nodemon (nodemon)

v3.1.10

Compare Source

Bug Fixes

• update types and jsdocs (#​2232) (297c7c7), closes #​2231

v3.1.9

Compare Source

Bug Fixes

• maintain backward support for exitcrash (9c9de6e)

v3.1.8

Compare Source

Bug Fixes

• types updated (cb91187)

v3.1.7

Compare Source

Bug Fixes

• types for export on ESModule (#​2211) (9b0606a)

v3.1.6

Compare Source

Bug Fixes

• watch nested paths (11fcaaa), closes #​2216

v3.1.5

Compare Source

Bug Fixes

• add missing ignore option to type defintion of config (#​2224) (254c2ab)

---

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: 08-node-express-uploading/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: multer-storage-cloudinary@4.0.0
npm error Found: cloudinary@2.7.0
npm error node_modules/cloudinary
npm error   cloudinary@"2.7.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer cloudinary@"^1.21.0" from multer-storage-cloudinary@4.0.0
npm error node_modules/multer-storage-cloudinary
npm error   multer-storage-cloudinary@"4.0.0" from the root project
npm error
npm error Conflicting peer dependency: cloudinary@1.41.3
npm error node_modules/cloudinary
npm error   peer cloudinary@"^1.21.0" from multer-storage-cloudinary@4.0.0
npm error   node_modules/multer-storage-cloudinary
npm error     multer-storage-cloudinary@"4.0.0" 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-03T01_52_52_858Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-03T01_52_52_858Z-debug-0.log