File Manager

X7ROOT File Manager

Current Path: /opt/alt/alt-nodejs19/root/usr/lib/node_modules/npm/lib/utils

opt / alt / alt-nodejs19 / root / usr / lib / node_modules / npm / lib / utils /

ðŸ“ ..
ðŸ“„ ansi-trim.js(173 B)
ðŸ“„ audit-error.js(1.02 KB)
ðŸ“„ auth.js(2.8 KB)
ðŸ“„ cmd-list.js(2.16 KB)
ðŸ“ completion
ðŸ“„ completion.fish(1.56 KB)
ðŸ“„ completion.sh(1.85 KB)
ðŸ“ config
ðŸ“„ did-you-mean.js(1.46 KB)
ðŸ“„ display.js(3.43 KB)
ðŸ“„ error-message.js(13.53 KB)
ðŸ“„ exit-handler.js(6.74 KB)
ðŸ“„ explain-dep.js(3.5 KB)
ðŸ“„ explain-eresolve.js(2.55 KB)
ðŸ“„ format-bytes.js(629 B)
ðŸ“„ format-search-stream.js(3.93 KB)
ðŸ“„ get-identity.js(802 B)
ðŸ“„ is-windows.js(233 B)
ðŸ“„ log-file.js(7.03 KB)
ðŸ“„ log-shim.js(1.68 KB)
ðŸ“„ npm-usage.js(2.04 KB)
ðŸ“„ open-url-prompt.js(1.44 KB)
ðŸ“„ open-url.js(1.09 KB)
ðŸ“„ otplease.js(1.23 KB)
ðŸ“„ ping.js(252 B)
ðŸ“„ pulse-till-done.js(412 B)
ðŸ“„ queryable.js(9.56 KB)
ðŸ“„ read-user-info.js(2 KB)
ðŸ“„ reify-finish.js(876 B)
ðŸ“„ reify-output.js(4.97 KB)
ðŸ“„ replace-info.js(807 B)
ðŸ“„ tar.js(3.9 KB)
ðŸ“„ timers.js(2.73 KB)
ðŸ“„ update-notifier.js(4.19 KB)
ðŸ“„ validate-lockfile.js(1023 B)
ðŸ“„ web-auth.js(558 B)

Editing: explain-eresolve.js

// 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.  It looks like:
// 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, noColor) => {
  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, noColor, Infinity)}\n\n${fix}`,
  }
}

module.exports = {
  explain,
  report,
}

X7ROOT File Manager

Editing: explain-eresolve.js

Upload File

Create Folder