aHub-Tech / hub-api

hub Api Backend
7 stars 3 forks source link

unable to resolve dependency tree #20

Closed RodrigoDornelles closed 3 years ago

RodrigoDornelles commented 3 years ago

quando executo npm audit fix ocorre este problema:

rodrigo@mac hub-api % npm audit fix
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: @nestjs/common@6.11.11
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"^6.11.8" from the root project
npm ERR!   peer @nestjs/common@"^6.0.0" from @nestjs/core@6.11.8
npm ERR!   node_modules/@nestjs/core
npm ERR!     @nestjs/core@"6.11.8" from the root project
npm ERR!     peer @nestjs/core@"^6.0.0 || ^7.0.0" from @nestjs/mongoose@6.4.0
npm ERR!     node_modules/@nestjs/mongoose
npm ERR!       @nestjs/mongoose@"^6.3.1" from the root project
npm ERR!     3 more (@nestjs/platform-express, @nestjs/swagger, nestjs-typegoose)
npm ERR!   7 more (@nestjs/jwt, @nestjs/mongoose, @nestjs/passport, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @nestjs/common@"^7.0.8" from @nestjs/mapped-types@0.4.0
npm ERR! node_modules/@nestjs/mapped-types
npm ERR!   @nestjs/mapped-types@"0.4.0" from @nestjs/swagger@4.8.0
npm ERR!   node_modules/@nestjs/swagger
npm ERR!     @nestjs/swagger@"^4.5.12" 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 /Users/rodrigo/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/rodrigo/.npm/_logs/2021-09-21T18_24_41_276Z-debug.log
DevRadhy commented 3 years ago

você tentou usar a flag --force junto com o comando

RodrigoDornelles commented 3 years ago

você tentou usar a flag --force junto com o comando

é correto fazer isso?

DevRadhy commented 3 years ago

você tentou usar a flag --force junto com o comando

é correto fazer isso?

o proprio audit pede para tentar com essa flag