chroma-core/chroma · error · Error

Failed to fetch package data: ${response.statusText}

Error message

Failed to fetch package data: ${response.statusText}

What it means

Error "Failed to fetch package data: ${response.statusText}" thrown in chroma-core/chroma.

Source

Thrown at clients/new-js/packages/chromadb/src/cli.ts:15

#!/usr/bin/env node
import semver from "semver";
import binding from "./bindings";

interface NpmPackageData {
  "dist-tags": {
    latest: string;
    [tag: string]: string;
  };
}

const getLatestVersion = async (packageName: string): Promise<string> => {
  const response = await fetch(`https://registry.npmjs.org/${packageName}`);
  if (!response.ok) {
    throw new Error(`Failed to fetch package data: ${response.statusText}`);
  }
  const data: NpmPackageData = await response.json();
  return data["dist-tags"].latest;
};

const update = async (): Promise<void> => {
  try {
    const installedVersion = process.env.CHROMADB_VERSION || "0.0.0";
    const latestVersion = await getLatestVersion("chromadb");

    if (semver.lt(installedVersion, latestVersion)) {
      console.log(`\nA new chromadb version (${latestVersion}) is available!`);
      console.log("\n\x1b[4mUpdat with npm\x1b[0m");
      console.log("npm install chromadb@latest");

      console.log("\n\x1b[4mUpdat with pnpm\x1b[0m");
      console.log("pnpm add chromadb@latest");

View on GitHub (pinned to aecdd12c8a)

When it happens

Trigger: Thrown at clients/new-js/packages/chromadb/src/cli.ts:15 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of chroma-core/chroma@aecdd12c8a (2026-08-16). Data as JSON: /api/errors/f378e16edd93c652. Report an issue: GitHub.