/usr/local/lib/node_modules/npm/lib/utils
NameSizeModeActions
audit-error.js10780644editdlrm
auth.js32880644editdlrm
cmd-list.js29530644editdlrm
completion.fish15960644editdlrm
completion.sh18980755editdlrm
did-you-mean.js11430644editdlrm
display.js167600644editdlrm
error-message.js157750644editdlrm
explain-dep.js36480644editdlrm
explain-eresolve.js25820644editdlrm
format-bytes.js6240644editdlrm
format-search-stream.js49130644editdlrm
format.js21400644editdlrm
get-identity.js7970644editdlrm
get-workspaces.js17480644editdlrm
installed-deep.js11290644editdlrm
installed-shallow.js5830644editdlrm
is-windows.js1770644editdlrm
log-file.js78600644editdlrm
npm-usage.js20720644editdlrm
oidc.js73680644editdlrm
open-url.js25530644editdlrm
output-error.js7880644editdlrm
ping.js2650644editdlrm
queryable.js96110644editdlrm
read-user-info.js20950644editdlrm
reify-finish.js7530644editdlrm
reify-output.js64750644editdlrm
sbom-cyclonedx.js56560644editdlrm
sbom-spdx.js52880644editdlrm
tar.js35110644editdlrm
timers.js21200644editdlrm
update-workspaces.js9970644editdlrm
validate-lockfile.js10230644editdlrm
verify-signatures.js124990644editdlrm
Edit: /usr/local/lib/node_modules/npm/lib/utils/explain-eresolve.js (2582B)
// this is called when an ERESOLVE error is caught in the exit-handler, or when there's a log.warn('eresolve', msg, explanation), to turn it into a human-intelligible explanation of what's wrong and how to fix. const { explainEdge, explainNode, printNode } = require('./explain-dep.js') // expl is an explanation object that comes from Arborist. // Depth is how far we want to want to descend into the object making a report. // The full report (ie, depth=Infinity) is always written to the cache folder at ${cache}/eresolve-report.txt along with full json. const explain = (expl, chalk, depth) => { const { edge, dep, current, peerConflict, currentEdge } = expl const out = [] const whileInstalling = dep && dep.whileInstalling || current && current.whileInstalling || edge && edge.from && edge.from.whileInstalling if (whileInstalling) { out.push('While resolving: ' + printNode(whileInstalling, chalk)) } // it "should" be impossible for an ERESOLVE explanation to lack both current and currentEdge, but better to have a less helpful error than a crashing failure. if (current) { out.push('Found: ' + explainNode(current, depth, chalk)) } else if (peerConflict && peerConflict.current) { out.push('Found: ' + explainNode(peerConflict.current, depth, chalk)) } else if (currentEdge) { out.push('Found: ' + explainEdge(currentEdge, depth, chalk)) } else /* istanbul ignore else - should always have one */ if (edge) { out.push('Found: ' + explainEdge(edge, depth, chalk)) } out.push('\nCould not resolve dependency:\n' + explainEdge(edge, depth, chalk)) if (peerConflict) { const heading = '\nConflicting peer dependency:' const pc = explainNode(peerConflict.peer, depth, chalk) out.push(heading + ' ' + pc) } return out.join('\n') } // generate a full verbose report and tell the user how to fix it const report = (expl, chalk, noColorChalk) => { const flags = [ expl.strictPeerDeps ? '--no-strict-peer-deps' : '', '--force', '--legacy-peer-deps', ].filter(Boolean) const or = (arr) => arr.length <= 2 ? arr.join(' or ') : arr.map((v, i, l) => i + 1 === l.length ? `or ${v}` : v).join(', ') const fix = `Fix the upstream dependency conflict, or retry this command with ${or(flags)} to accept an incorrect (and potentially broken) dependency resolution.` return { explanation: `${explain(expl, chalk, 4)}\n\n${fix}`, file: `# npm resolution error report\n\n${explain(expl, noColorChalk, Infinity)}\n\n${fix}`, } } module.exports = { explain, report, }