Dependency conflict with reflect-metadata when install with NestJS

[Skryabind]

Is there an existing issue for this?

• I have searched the existing issues

Describe the issue

I have installed NestJs and have reflect-metadata in my dependencies:
"reflect-metadata": "^0.2.0"

I try to install automapper libs:
npm i --save @automapper/core @automapper/nestjs @automapper/classes reflect-metadata
and get a error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: api@0.0.1
npm ERR! Found: reflect-metadata@0.2.1
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"^0.2.0" from api@0.0.1
npm ERR!   api
npm ERR!     api@0.0.1
npm ERR!     node_modules/api
npm ERR!       workspace api from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"~0.1.13" from @automapper/classes@8.8.1
npm ERR! node_modules/@automapper/classes
npm ERR!   @automapper/classes@"*" from api@0.0.1
npm ERR!   api
npm ERR!     api@0.0.1
npm ERR!     node_modules/api
npm ERR!       workspace api 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! 

I found that @automapper/classes has fixed version of reflect-metadata 0.1.13 ans it's conflicted with new versions like 0.2.0.
Can automapper/classes be updated to the latest version of reflect-metadata, or maybe there is some other way to fix a problem?

Models/DTOs/VMs

No response

Mapping configuration

No response

Steps to reproduce

1. Add "reflect-metadata": "^0.2.0" in your project dependencies.
2. Install automapper libs:
   npm i --save @automapper/core @automapper/nestjs @automapper/classes

Expected behavior

Expect to automapper can be installed with the latest reflect-metadata lib

Screenshots

No response

Minimum reproduction code

No response

Package

• I don't know.
• @automapper/core
• @automapper/classes
• @automapper/nestjs
• @automapper/pojos
• @automapper/mikro
• @automapper/sequelize
• Other (see below)

Other package and its version

No response

AutoMapper version

8.0.0

Additional context

Linux
node v16.20.1

[TeoConan]

Same bug here...

[KroniKZA]

Any idea when approval on the PR will come in?

[irazers]

in the meantime you can use npm install --legacy-peer-deps (but I agree it is not clean)

[swang2019]

same issue

[e-lag]

same issue

[chriso86]

Weird, there is a PR for this and it looks like the last update on this repo was 10 months ago.
I wouldn't use it in this state as it seems abandoned at the moment.
Does only one person have control over this repo?

[neekey]

same issue here

[hx-run]

Same issue is continue

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: Consilium@0.0.1
npm error Found: reflect-metadata@0.2.2
npm error node_modules/reflect-metadata
npm error   reflect-metadata@"^0.2.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer reflect-metadata@"~0.1.13" from @automapper/classes@8.8.1
npm error node_modules/@automapper/classes
npm error   @automapper/classes@"*" 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 /Users/hxrun/.npm/_logs/2025-01-19T12_25_48_696Z-eresolve-report.txt
npm error A complete log of this run can be found in: /Users/hxrun/.npm/_logs/2025-01-19T12_25_48_696Z-debug-0.log

[brdar]

Fixed in fork: https://github.com/brdar/mapper-js