Closed antongolub closed 3 years ago
npx yarn-audit-fix --npm.legacy-peer-deps --npm.force
Preparing temp assets... Generating package-lock.json from yarn.lock... Applying npm audit fix... invoke /Users/foobar/.npm/_npx/54991/lib/node_modules/yarn-audit-fix/node_modules/.bin/npm audit fix --package-lock-only --prefix /Users/antongolub/projects/js-platform/node_modules/.cache/yarn-audit-fix/0fbe724a7952b7542c6533ff6fbe679a npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: @qiwi-private/js-platform-infra@1.0.1 npm ERR! Found: typescript@4.2.3 npm ERR! node_modules/typescript npm ERR! dev typescript@"^4.1.2" from infra@1.0.1 npm ERR! packages/infra npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer typescript@"3.9.x || 4.0.x" from typedoc@0.19.2 npm ERR! node_modules/typedoc npm ERR! dev typedoc@"^0.19.2" from infra@1.0.1 npm ERR! packages/infra 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/foobar/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /Users/foobar/.npm/_logs/2021-03-22T19_33_17_085Z-debug.log { status: 1, signal: null, output: [ null, null, null ], pid: 55002, stdout: null, stderr: null }
Custom flags can significantly affect util behaviour, so that would be difficult to handle correctly.