fix(deps): update dependency reflect-metadata to ^0.2.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
reflect-metadata (source)	^0.1.13 -> ^0.2.0

---

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 #​155
• Update main to v0.2.1 by @​rbuckton in #​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 #​144
• No dynamic evaluation in /lite mode by @​rbuckton in #​149

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

v0.1.14: reflect-metadata 0.1.14

Compare Source

What's Changed

• Fix variable name by @​amatiasq in #​109
• Bypass webpack process.env inlining by @​rbuckton in c8c06cc

New Contributors

• @​amatiasq made their first contribution in #​109

Full Changelog: microsoft/reflect-metadata@v0.1.13...v0.1.14

---

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: @nestjs/common@10.2.10
npm ERR! Found: reflect-metadata@0.2.1
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"^0.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@10.2.10
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"^10.0.0" from the root project
npm ERR!   peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/apollo@12.0.11
npm ERR!   node_modules/@nestjs/apollo
npm ERR!     @nestjs/apollo@"12.0.11" from the root project
npm ERR!   8 more (@nestjs/config, @nestjs/core, @nestjs/graphql, ...)
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@10.2.10
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"^10.0.0" from the root project
npm ERR!     peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/apollo@12.0.11
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR!     8 more (@nestjs/config, @nestjs/core, @nestjs/graphql, ...)
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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-12-15T05_24_56_289Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-12-15T05_24_56_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 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: @nestjs/common@10.2.10
npm error Found: reflect-metadata@0.2.2
npm error node_modules/reflect-metadata
npm error   reflect-metadata@"^0.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer reflect-metadata@"^0.1.12" from @nestjs/common@10.2.10
npm error node_modules/@nestjs/common
npm error   @nestjs/common@"^10.0.0" from the root project
npm error   peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/apollo@12.0.11
npm error   node_modules/@nestjs/apollo
npm error     @nestjs/apollo@"12.0.11" from the root project
npm error   8 more (@nestjs/config, @nestjs/core, @nestjs/graphql, ...)
npm error
npm error Conflicting peer dependency: reflect-metadata@0.1.14
npm error node_modules/reflect-metadata
npm error   peer reflect-metadata@"^0.1.12" from @nestjs/common@10.2.10
npm error   node_modules/@nestjs/common
npm error     @nestjs/common@"^10.0.0" from the root project
npm error     peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/apollo@12.0.11
npm error     node_modules/@nestjs/apollo
npm error       @nestjs/apollo@"12.0.11" from the root project
npm error     8 more (@nestjs/config, @nestjs/core, @nestjs/graphql, ...)
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-11-19T15_56_29_832Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-19T15_56_29_832Z-debug-0.log