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
IMPACT UPDATE: not updating lets packages go stale, increasing the likelihood packages will have vulnerabilities and allow our systems to be compromised.
Dependency issues are preventing automated PRs from running smoothly. Do not use --force, since this only ignores the issue!
E.g.:
File name: libs/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @nestjs/common@9.4.3
npm ERR! Found: reflect-metadata@0.2.1
npm ERR! node_modules/reflect-metadata
npm ERR! dev reflect-metadata@"^0.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@9.4.3
npm ERR! node_modules/@nestjs/common
npm ERR! @nestjs/common@"^9.4.0" from the root project
npm ERR! peer @nestjs/common@"^9.0.0" from @nestjs/core@9.4.3
npm ERR! node_modules/@nestjs/core
npm ERR! @nestjs/core@"^9.4.0" from the root project
npm ERR! 1 more (@nestjs/testing)
npm ERR! 1 more (@nestjs/testing)
npm ERR!
npm ERR! Conflicting peer dependency: reflect-metadata@0.1.14
npm ERR! node_modules/reflect-metadata
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@9.4.3
npm ERR! node_modules/@nestjs/common
npm ERR! @nestjs/common@"^9.4.0" from the root project
npm ERR! peer @nestjs/common@"^9.0.0" from @nestjs/core@9.4.3
npm ERR! node_modules/@nestjs/core
npm ERR! @nestjs/core@"^9.4.0" from the root project
npm ERR! 1 more (@nestjs/testing)
npm ERR! 1 more (@nestjs/testing)
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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-01-02T21_01_57_656Z-debug-0.log
The text was updated successfully, but these errors were encountered:
IMPACT UPDATE: not updating lets packages go stale, increasing the likelihood packages will have vulnerabilities and allow our systems to be compromised.
Dependency issues are preventing automated PRs from running smoothly. Do not use
--force
, since this only ignores the issue!E.g.:
The text was updated successfully, but these errors were encountered: