feat: loosen reflect-metadata peerDependency for Nest v10 #178
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following occurs when trying to install nest-authz in a Nest.js 10.0.0 project.
❯ npm i nest-authz
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/reflect-metadata
npm error reflect-metadata@"^0.2.0" from the root project
npm error peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm error node_modules/@nestjs/common
npm error @nestjs/common@"^10.0.0" from the root project
npm error peer @nestjs/common@"^9.0.3 || ^10.0.0" from [email protected]
npm error node_modules/nest-authz
npm error nest-authz@"" from the root project
npm error 5 more (@nestjs/core, @nestjs/microservices, ...)
npm error 3 more (@nestjs/core, @nestjs/microservices, @nestjs/websockets)
npm error
npm error Could not resolve dependency:
npm error peer reflect-metadata@"^0.1.13" from [email protected]
npm error node_modules/nest-authz
npm error nest-authz@"" 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.