You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The last version of typeorm (0.3.20) uses mongodb@6.x.x in its devDependencies, but mongodb@5.x.x in its peerDependencies, which causes a dependency conflict with mongodb@6.x.x
Expected Behavior
The version of typeorm's mongodb should be compatible with mongodb@6.x.x
Actual Behavior
I get the following error when I try to run npm i:
npm ERR! Could not resolve dependency:
npm ERR! peerOptional mongodb@"^5.8.0" from typeorm@0.3.20
npm ERR! node_modules/typeorm
npm ERR! typeorm@"^0.3.20" from the root project
npm ERR! peer typeorm@"^0.3.0" from @nestjs/typeorm@10.0.2
npm ERR! node_modules/@nestjs/typeorm
npm ERR! @nestjs/typeorm@"^10.0.1" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: mongodb@5.9.2
npm ERR! node_modules/mongodb
npm ERR! peerOptional mongodb@"^5.8.0" from typeorm@0.3.20
npm ERR! node_modules/typeorm
npm ERR! typeorm@"^0.3.20" from the root project
npm ERR! peer typeorm@"^0.3.0" from @nestjs/typeorm@10.0.2
npm ERR! node_modules/@nestjs/typeorm
npm ERR! @nestjs/typeorm@"^10.0.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.
Issue description
The last version of typeorm (0.3.20) uses mongodb@6.x.x in its devDependencies, but mongodb@5.x.x in its peerDependencies, which causes a dependency conflict with mongodb@6.x.x
Expected Behavior
The version of typeorm's mongodb should be compatible with mongodb@6.x.x
Actual Behavior
I get the following error when I try to run
npm i
:(I can't use
--force
in certain circumstances)Steps to reproduce
My Environment
Additional Context
No response
Relevant Database Driver(s)
Are you willing to resolve this issue by submitting a Pull Request?
No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.
The text was updated successfully, but these errors were encountered: