nodejs/node · error · Error

Some problems found. See above for recommendations.

Error message

Some problems found. See above for recommendations.

What it means

Same failure path as the silent variant, but here npm is NOT silent, so the message tells you the per-check 'Not ok' lines and recommendations are printed above the throw. The fix is to read those lines and resolve each named problem.

Source

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

    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. Scroll up to the 'Not ok' lines and fix each named check individually
2. Re-run `npm doctor` after each fix to confirm progress
3. For environmental issues, update PATH, install git, free/repair the cache, or upgrade node

// No pre-check prevents environmental failures; run doctor and triage output
async function runDoctor() {
  try { await runNpm('doctor') } catch (e) { /* collect Not-ok lines */ }
}

try {
  await runNpm('doctor')
} catch (e) {
  if (/problems found/i.test(e.message)) { triageDoctorOutput() /* parse Not-ok lines */ }
  else throw e
}

When it happens

Trigger: Running `npm doctor` (normal verbosity) when at least one check fails — e.g. globalBin not on PATH, git missing, cache not writable, registry unreachable, node older than recommended.

Common situations: Fresh machines, hardened/minimal containers, misconfigured PATH, restricted corporate networks blocking the registry ping.

Related errors

• Some problems found. Check logs or disable silent mode for r
• 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/6a1b251df66df7f7. Report an issue: GitHub.