Solucionar conflicto con paquete npm install

Tiempo de lectura: < 1 minuto

Si al instalar un paquete nos sale un texto de error como este:

npm WARN config global --global, --local are deprecated. Use --location=global instead.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @react-navigation/stack@6.2.2
npm ERR! Found: @react-navigation/native@5.9.8
npm ERR! node_modules/@react-navigation/native
npm ERR! @react-navigation/native@»^5.9.8″ from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @react-navigation/native@»^6.0.0″ from @react-navigation/stack@6.2.2
npm ERR! node_modules/@react-navigation/stack
npm ERR! @react-navigation/stack@»^6.2.2″ from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @react-navigation/native@6.0.11
npm ERR! node_modules/@react-navigation/native
npm ERR! peer @react-navigation/native@»^6.0.0″ from @react-navigation/stack@6.2.2
npm ERR! node_modules/@react-navigation/stack
npm ERR! @react-navigation/stack@»^6.2.2″ 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.

Quiere decir que una dependencia tiene un conflicto.

Para poder instalar dicha dependencia introducimos este comando de instalación:

npm install --legacy-peer-deps