fix(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.13 -> ^0.1.13 || ^0.2.0
reflect-metadata (source)	0.1.13 -> 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: microsoft/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: microsoft/reflect-metadata@v0.1.14...v0.2.0

v0.1.14

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 these updates 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 artifacts 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: @nestjs/common@8.4.1
npm ERR! Found: reflect-metadata@0.2.2
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR! node_modules/@nestjs/common
npm ERR!   dev @nestjs/common@"8.4.1" from the root project
npm ERR!   peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!   node_modules/@nestjs/core
npm ERR!     dev @nestjs/core@"8.4.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: reflect-metadata@0.1.14
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"8.4.1" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!     node_modules/@nestjs/core
npm ERR!       dev @nestjs/core@"8.4.1" 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-26T13_49_42_001Z-debug-0.log

File name: demo/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/common@8.4.1
npm ERR! Found: reflect-metadata@0.2.2
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"8.4.1" from the root project
npm ERR!   peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!   node_modules/@nestjs/core
npm ERR!     @nestjs/core@"8.4.1" from the root project
npm ERR!     3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
npm ERR!   3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
npm ERR! 
npm ERR! Conflicting peer dependency: reflect-metadata@0.1.14
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"8.4.1" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!     node_modules/@nestjs/core
npm ERR!       @nestjs/core@"8.4.1" from the root project
npm ERR!       3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
npm ERR!     3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
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-26T13_49_48_486Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts 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: @nestjs/common@8.4.1
npm ERR! Found: reflect-metadata@0.2.2
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR! node_modules/@nestjs/common
npm ERR!   dev @nestjs/common@"8.4.1" from the root project
npm ERR!   peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!   node_modules/@nestjs/core
npm ERR!     dev @nestjs/core@"8.4.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: reflect-metadata@0.1.14
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"8.4.1" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!     node_modules/@nestjs/core
npm ERR!       dev @nestjs/core@"8.4.1" 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-03-02T14_42_39_579Z-debug-0.log

File name: demo/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/common@8.4.1
npm ERR! Found: reflect-metadata@0.2.2
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"8.4.1" from the root project
npm ERR!   peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!   node_modules/@nestjs/core
npm ERR!     @nestjs/core@"8.4.1" from the root project
npm ERR!     3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
npm ERR!   3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
npm ERR! 
npm ERR! Conflicting peer dependency: reflect-metadata@0.1.14
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"8.4.1" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!     node_modules/@nestjs/core
npm ERR!       @nestjs/core@"8.4.1" from the root project
npm ERR!       3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
npm ERR!     3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
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-03-02T14_42_42_933Z-debug-0.log

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^0.1.13 || ^0.2.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.