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

vantadb-node

v0.9.0

Published

VantaDB native Node.js bindings via napi-rs — persistent embedded memory & vector search (additional backend to WASM)

Readme

vantadb-node

Status: active (core-promise until 1.0 — one of the three active language connectors; cross-language parity guard).

VantaDB native Node.js bindings via napi-rs — persistent embedded memory & vector search, with graph traversal and hybrid search. The native backend to vantadb-ts (WASM).

Full reference: docs/api/NODE_SDK.md is the canonical source (quickstart, native-vs-WASM matrix, per-runtime examples, full API incl. lifecycle/maintenance/advanced search). This README is a minimal pointer — details live there.

Estado 2026-09-09: paquete pre-npm (instalación desde source; npm pack incluye el prebuild *.node verificado). Ver docs/dev/reviews/archive/research-vantadb-node-20260825.md para el plan de distribución y docs/dev/tasks/TS-12.md para la checklist del publish humano.

Instalación (source)

git clone <repo> && cd vantadb-node
npm install          # @napi-rs/cli + vitest
npm run build        # napi build --platform --release (requiere Rust)

Requisitos: Node ≥ 18 (este paquete) · Rust stable. Compat: vantadb-ts exige Node ≥ 22.19 (vantadb-ts/package.json:engines).

Uso

import { VantaDb } from "vantadb-node";

const db = await VantaDb.connect("./data");   // o ":memory:"
await db.put({ namespace: "agent/main", key: "pref-1", payload: "usa TypeScript" });

const hit = await db.search({
  namespace: "agent/main",
  query_vector: [...],
  text_query: "typescript",
});
console.log(hit.hits[0].record.payload, hit.hits[0].score);

// Grafo dirigido con traversal filtrada
await db.addEdge("1", "2", "depends_on");
const dag = await db.graphIsDag(["1"]);

await db.close();   // drena operaciones in-flight antes de flush

API (VantaDb — todos async)

| Área | Métodos | |------|---------| | Ciclo de vida | connect(path, {read_only?, memory_limit?}) · flush() · close() | | Memoria | put(record) · putBatch(records) · get(ns, key) · delete(ns, key) · list(ns, {filters?, limit?, cursor?}) · listNamespaces() | | Búsqueda | search(request) (vector+filters+text, hybrid) · explainSearch(request) | | Grafo | insertNode · getNode · deleteNode(id, reason) · addEdge · removeEdge · graphBfs/Dfs/TopologicalSort/IsDag/FilteredTraversal/Degree | | Runtime | capabilities() |

Los ids de grafo viajan como decimal strings (u128 > Number.MAX_SAFE_INTEGER).

Native vs WASM — cuándo usar cada uno

| | vantadb-node (nativo) | vantadb-ts (WASM) | |---|---|---| | Node.js / Bun (backend, CLIs, agentes) | ✅ recomendado | ✅ funciona | | Browser / edge runtime | ❌ | ✅ único camino | | Performance | nativa (benchmark A/B pendiente — H-09) | buena, con overhead wasm |

Tests

npm test            # vitest run

Licencia

Apache-2.0