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

@melandlabs/rag

v0.3.0

Published

OpenContext · rag module

Readme

rag (workspace)

Workspace package. Internal monorepo build artifact; not published to npm. End users install @melandlabs/opencontext (the facade) instead. Monorepo contributors depend on this package via the workspace protocol.

Core Retrieval-Augmented Generation primitives without the AI SDK runtime overhead. Suitable for lightweight or backend-only consumers that only need chunking, embeddings, parsers, and a vector store.

Installation

pnpm add @melandlabs/opencontext

Subpath Exports

  • rag — Main entrypoint
  • rag/chunking — Document chunking strategies
  • rag/embeddings — Embedding generation helpers
  • rag/vector-service — High-level vector service facade
  • rag/parsers — Document parsers (PDF, ZIP, plain text)
  • rag/universal-embeddings — Universal embedding interface
  • rag/sqlite-vec-store — sqlite-vec vector store adapter
  • rag/pgvector-store — pgvector vector store adapter
  • rag/lancedb-store — embedded/local LanceDB hybrid store
  • rag/milvus-store — external Milvus hybrid store
  • rag/hybrid-search — fusion adapter for an existing vector and lexical store

Hybrid retrieval

LanceDB and Milvus implement dense vector retrieval plus BM25/full-text retrieval. Reciprocal Rank Fusion (RRF) is the default because the two branches use different score scales; weighted, min-max-normalized fusion is also available.

Install only the backend used by the host application:

pnpm add @lancedb/lancedb
# or
pnpm add @zilliz/milvus2-sdk-node

Configure LanceDB for an embedded/local deployment:

import {
  configureVectorService,
  searchHybridVectorStore,
} from "@melandlabs/opencontext";

configureVectorService({
  backend: "lancedb",
  lancedb: { uri: "./data/lancedb" },
  hybrid: { fusion: "rrf", candidateMultiplier: 4 },
});

const matches = await searchHybridVectorStore({
  text: "invoice-2024-017",
  vector: queryEmbedding,
  limit: 10,
  filter: { userId },
});

For a Milvus 2.5+ service, configure the server address and the embedding dimension. The adapter creates one collection containing a dense vector and a BM25-generated sparse vector:

configureVectorService({
  backend: "milvus",
  milvus: {
    address: "localhost:19530",
    dimension: 1536,
  },
  hybrid: { fusion: "weighted", alpha: 0.65 },
});

Existing sqlite-vec, pgvector, and custom factories remain valid. The hybrid helper falls back to their existing dense similaritySearch implementation, so enabling the new adapters does not require migrating existing data. Use HybridSearchAdapter when the application already has a separate lexical search provider and wants to add fusion without changing its vector store.