rohitg00/agentmemory · warning

No package manager found (pnpm/npm). Skipping JS dependency

Error message

No package manager found (pnpm/npm). Skipping JS dependency upgrade.

What it means

A warning emitted by the `upgrade` command when neither pnpm nor npm is found on PATH, so the JS dependency upgrade (including pinning iii-sdk@0.11.2) is skipped. The upgrade continues to the next step (engine reinstall prompt).

Source

Thrown at src/cli.ts:3194

      const installOk = runCommand(pnpmBin, ["install"], {
        label: "Refreshing dependencies (pnpm install)",
      });
      requireSuccess(installOk, "pnpm install");
      runCommand(pnpmBin, ["up", "iii-sdk@0.11.2"], {
        label: "Pinning iii-sdk@0.11.2",
        optional: true,
      });
    } else if (npmBin) {
      const installOk = runCommand(npmBin, ["install"], {
        label: "Refreshing dependencies (npm install)",
      });
      requireSuccess(installOk, "npm install");
      runCommand(npmBin, ["install", "iii-sdk@0.11.2"], {
        label: "Pinning iii-sdk@0.11.2",
        optional: true,
      });
    } else {
      p.log.warn("No package manager found (pnpm/npm). Skipping JS dependency upgrade.");
    }
  } else {
    p.log.warn("No package.json in current directory. Skipping JS dependency upgrade.");
  }

  const upgradeEngine = await p.confirm({
    message: "Re-run the iii-engine install script (curl | sh)?",
    initialValue: true,
  });
  if (p.isCancel(upgradeEngine)) {
    p.cancel("Cancelled.");
    return process.exit(0);
  }
  if (upgradeEngine === true) {
    await runIiiInstaller();
  } else {
    p.log.info("Skipped iii-engine installer.");
  }

View on GitHub (pinned to e04ba88819)

Solutions

  1. Install Node.js/npm (or pnpm) and ensure it is on PATH, then re-run the upgrade
  2. Run the dependency upgrade manually: npm install iii-sdk@0.11.2
  3. Re-run the upgrade inside the shell where your Node version manager is initialized

Example fix

// before
$ PATH=/usr/local/minimal-bin agentmemory upgrade
// after
$ export PATH="$(npm config get prefix)/bin:$PATH"
$ npm install -g npm && agentmemory upgrade
Defensive patterns

Strategy: fallback

Validate before calling

const pm = ["pnpm","npm"].find(b => { try { require("child_process").execSync(`${b} --version`, {stdio:"ignore"}); return true; } catch { return false; } });
if (!pm) console.warn("No pnpm/npm on PATH; JS dependency upgrade will be skipped.");

Prevention

When it happens

Trigger: Running the agentmemory upgrade flow in a directory with a package.json when no `pnpm` or `npm` binary is resolvable on PATH.

Common situations: Node not installed globally (e.g. using only volta/nvm without shims initialized), non-Node project envs, Docker images without npm, PATH misconfiguration in CI.

Related errors


AI-assisted analysis of rohitg00/agentmemory@e04ba88819 (2026-08-30). Data as JSON: /api/errors/03b8b8faa102fbff. Report an issue: GitHub.