nodejs/node · error · Error

Some problems found. Check logs or disable silent mode for r

Error message

Some problems found. Check logs or disable silent mode for recommendations.

What it means

`npm doctor` runs several health checks and tracks an allOk flag. If any check throws and npm is in silent mode, it throws this terse message telling you to consult logs or disable silent mode for the per-check detail.

Source

Thrown at deps/npm/lib/commands/doctor.js:128

    const actions = this.actions(args)

    const chalk = this.npm.chalk
    for (const { title, cmd } of actions) {
      this.output(title)
      // TODO when we have an in progress indicator that could go here
      let result
      try {
        result = await this[cmd]()
        this.output(`${chalk.green('Ok')}${result ? `\n${result}` : ''}\n`)
      } catch (err) {
        allOk = false
        this.output(`${chalk.red('Not ok')}\n${chalk.cyan(err)}\n`)
      }
    }

    if (!allOk) {
      if (this.npm.silent) {
        throw new Error('Some problems found. Check logs or disable silent mode for recommendations.')
      } else {
        throw new Error('Some problems found. See above for recommendations.')
      }
    }
  }

  async checkPing () {
    log.info('doctor', 'Pinging registry')
    try {
      await ping({ ...this.npm.flatOptions, retry: false })
      return ''
    } catch (er) {
      if (/^E\d{3}$/.test(er.code || '')) {
        throw er.code.slice(1) + ' ' + er.message
      } else {
        throw er.message
      }
    }

View on GitHub (pinned to 1b2de5e052)

Solutions

1. Re-run without silent mode to see which check failed and its recommendation
2. Address the failing check (registry connectivity, cache permissions, global bin on PATH, git availability, node version)
3. If silence is required, inspect the log file npm wrote (path shown in npm's log output)

Example fix

# before
npm doctor --silent

# after
npm doctor

// Avoid silent mode for diagnostic commands
function safeDoctorArgs(args) {
  return args.filter(a => a !== '--silent' && a !== '-s' && a !== '--loglevel=silent')
}

function isSilentInvocation(args) {
  return args.some(a => a === '--silent' || a === '-s' || /^--loglevel=silent$/.test(a))
}

try {
  await runNpm('doctor', !verbose ? [] : [])
} catch (e) {
  if (/disable silent mode/.test(e.message)) { await runNpm('doctor') /* retry verbose */ }
  else throw e
}

When it happens

Trigger: Running `npm doctor` with --silent, -s, --loglevel=silent, or npm_config_loglevel=silent, while one or more checks (ping, cache perms, PATH, node version, git, etc.) fail.

Common situations: CI that runs npm with silent logging by default; wrappers that set a global quiet flag.

Related errors

• Some problems found. See above for recommendations.
• Cannot use --no-workspaces and --workspace at the same time
• Please provide only one of ${flagList}
• Unknown positional argument: ${extra}
• ${argv[2]} not recognized

AI-assisted analysis of nodejs/node@1b2de5e052 (2026-08-13). Data as JSON: /api/errors/cdd9bd573ebcf617. Report an issue: GitHub.