npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

chromadb-ui

v1.0.0-beta.13

Published

A React UI component library for ChromaDB integration

Downloads

8

Readme

ChromaDB UI

A React UI library for ChromaDB that provides a complete interface for managing ChromaDB collections, including connection management, collection operations, and data visualization.

Features

  • Connection management with ChromaDB server
  • Collection creation and deletion
  • Collection listing and management
  • Support for custom embedding functions
  • Built with Tailwind CSS for modern, responsive design
  • TypeScript support
  • Zero-config setup with default embedding function

Installation

npm install chromadb-ui
# or
yarn add chromadb-ui

Requirements

1. Required Peer Dependencies

The following packages are required as peer dependencies:

npm install chromadb @xenova/transformers chromadb-default-embed

2. Tailwind CSS Configuration

This library uses Tailwind CSS utility classes. Your project must have Tailwind CSS installed and configured:

  1. Install Tailwind in your project if you haven't already:
npm install -D tailwindcss
npx tailwindcss init
  1. Configure your tailwind.config.js to include the chromadb-ui components:
/** @type {import('tailwindcss').Config} */
module.exports = {
  content: [
    "./src/**/*.{js,jsx,ts,tsx}",
    "./node_modules/chromadb-ui/**/*.{js,jsx,ts,tsx}" // Add this line
  ],
  theme: {
    extend: {},
  },
  plugins: [],
}
  1. Import Tailwind CSS in your main CSS file:
@tailwind base;
@tailwind components;
@tailwind utilities;

Usage

Basic Usage

import { ChromaDBUI } from 'chromadb-ui';

function App() {
  return (
    <div>
      <ChromaDBUI />
    </div>
  );
}

With Custom Configuration

import { ChromaDBUI } from 'chromadb-ui';

function App() {
  return (
    <div>
      <ChromaDBUI
        defaultConfig={{
          serverUrl: 'http://localhost:8000',
          tenant: 'default_tenant',
          database: 'default_database'
        }}
      />
    </div>
  );
}

Individual Components Usage

You can also use individual components from the library:

import { 
  ChromaDBProvider, 
  ConnectionPanel, 
  CollectionsPanel 
} from 'chromadb-ui';

function App() {
  return (
    <ChromaDBProvider>
      <div className="p-6">
        <ConnectionPanel />
        <CollectionsPanel />
      </div>
    </ChromaDBProvider>
  );
}

API Reference

ChromaDBUI Props

| Prop | Type | Description | Default | |------|------|-------------|---------| | defaultConfig | ChromaDBConfig | Initial configuration for ChromaDB connection | undefined |

ChromaDBConfig Interface

interface ChromaDBConfig {
  serverUrl: string;
  tenant?: string;
  database?: string;
}

ChromaDBProvider Context

The ChromaDBProvider context provides the following values:

interface ChromaDBContextType {
  client: ChromaClient | null;
  collections: string[];
  loading: boolean;
  error: string | null;
  connected: boolean;
  currentConfig: ConnectionConfig | null;
  embeddingFunction: any;
  connect: (config: ConnectionConfig) => Promise<void>;
  disconnect: () => void;
  createCollection: (params: CreateCollectionParams) => Promise<void>;
  deleteCollection: (name: string) => Promise<void>;
  refreshCollections: () => Promise<void>;
}

Development

  1. Clone the repository
git clone https://github.com/yourusername/chromadb-ui.git
cd chromadb-ui
  1. Install dependencies
npm install
  1. Build
npm run build

Local Testing

To test the library locally:

  1. Link the package:
npm link
  1. In your test project:
npm link chromadb-ui
  1. Make changes to the library
  2. Rebuild the library:
npm run build

Changes will be reflected in your test project automatically.

Troubleshooting

Common Issues

  1. Connection Issues

    • Ensure ChromaDB server is running and accessible
    • Check the server URL in your configuration
    • Verify network connectivity
    • Also ensure to set cors for the url of chromadb
  2. Styling Issues

    • Verify Tailwind CSS is properly configured
    • Check if the content array in tailwind.config.js includes the chromadb-ui path
  3. Build Issues

    • Ensure all peer dependencies are installed
    • Check TypeScript version compatibility

License

GNU GENERAL PUBLIC LICENSE

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Support

For support, please:

  1. Check the GitHub Issues
  2. Create a new issue if your problem hasn't been addressed

Future Development

  • Add support for custom embedding functions
  • Add collection querying interface
  • Add data visualization components
  • Add batch operations support
  • Add more configuration options