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

@0xx0lostcause0xx0/polypack-native

v3.4.1

Published

NAPI-RS bindings exposing the polypack-core vector engine to Node.js

Readme

@0xx0lostcause0xx0/polypack-native

NAPI-RS bindings exposing the polypack-core Rust engine to Node.js: vector indexes, the query-plan executor, and the directory-backed persistence store, as drop-in accelerators for @0xx0lostcause0xx0/polypack.

This package ships prebuilt binaries via optional dependencies for darwin-x64, darwin-arm64, linux-x64-gnu, linux-arm64-gnu, and win32-x64-msvc. If no native binary is available for the current platform, isNativeAvailable() reports false and callers should fall back to the pure-TypeScript engine — this package does not do that fallback for you.

Install

npm install @0xx0lostcause0xx0/polypack-native

Usage

import { isNativeAvailable, NativeVectorIndex, NativeHnswIndex, NativeStore } from '@0xx0lostcause0xx0/polypack-native'

if (isNativeAvailable()) {
  const index = new NativeVectorIndex(undefined, 'cosine')
  index.add('doc_1', [0.95, 0.20, 0.10])
  index.query([0.90, 0.30, 0.10], 5, 0.5)
}

NativeVectorIndex and NativeHnswIndex are drop-in replacements for the TypeScript VectorIndex/HNSWIndex classes, and createNativeVectorIndex() plugs directly into PolyGraph's createVectorIndex constructor hook (typed as VectorIndexLike, so this type-checks under tsc --strict):

import { PolyGraph } from '@0xx0lostcause0xx0/polypack'
import { createNativeVectorIndex } from '@0xx0lostcause0xx0/polypack-native'

const graph = new PolyGraph(undefined, 50_000, undefined, undefined, createNativeVectorIndex())

installNativeQueryExecutor() routes in-memory GraphQuery execution through the Rust query planner when available (queries with join predicates still fall back to TypeScript). NativeStore is a directory-backed store using the same snapshot/WAL byte format as the TypeScript BinaryStoreAdapter, so files are interchangeable between the two.

None of this wiring happens automatically — importing this package does not change @0xx0lostcause0xx0/polypack's behavior on its own; call the hooks above explicitly.

API

See src/index.d.ts for the full exported surface: NativeVectorIndex, NativeHnswIndex, NativeStore, executeQueryPlan, aggregateQueryPlan, installNativeQueryExecutor, engineInfo, isNativeAvailable, and detectEngine.

License

MIT