chore(deps): update dependency reflect-metadata to v0.2.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
reflect-metadata (source)	0.1.14 -> 0.2.2

---

Release Notes

rbuckton/reflect-metadata (reflect-metadata)

v0.2.2

Compare Source

v0.2.1

Compare Source

What's Changed

• Fix stack overflow crash in isProviderFor by @​rbuckton in https://github.com/rbuckton/reflect-metadata/pull/155
• Update main to v0.2.1 by @​rbuckton in https://github.com/rbuckton/reflect-metadata/pull/156

Full Changelog: rbuckton/reflect-metadata@v0.2.0...v0.2.1

v0.2.0: reflect-metadata 0.2.0

Compare Source

What's Changed

• Add /lite and /no-conflict exports by @​rbuckton in https://github.com/rbuckton/reflect-metadata/pull/144
• No dynamic evaluation in /lite mode by @​rbuckton in https://github.com/rbuckton/reflect-metadata/pull/149

Full Changelog: rbuckton/reflect-metadata@v0.1.14...v0.2.0

---

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 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/[email protected]
npm error Found: [email protected]
npm error node_modules/reflect-metadata
npm error   dev reflect-metadata@"0.2.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm error node_modules/@nestjs/common
npm error   dev @nestjs/common@"9.4.3" from the root project
npm error   peer @nestjs/common@"^9.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/core
npm error     dev @nestjs/core@"9.4.3" from the root project
npm error     2 more (@nestjs/microservices, @nestjs/testing)
npm error   2 more (@nestjs/microservices, @nestjs/testing)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/reflect-metadata
npm error   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm error   node_modules/@nestjs/common
npm error     dev @nestjs/common@"9.4.3" from the root project
npm error     peer @nestjs/common@"^9.0.0" from @nestjs/[email protected]
npm error     node_modules/@nestjs/core
npm error       dev @nestjs/core@"9.4.3" from the root project
npm error       2 more (@nestjs/microservices, @nestjs/testing)
npm error     2 more (@nestjs/microservices, @nestjs/testing)
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 /tmp/renovate/cache/others/npm/_logs/2024-05-08T01_37_09_780Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-08T01_37_09_780Z-debug-0.log