Proposal: official Node.js binding (turbovec-node)

[beshkenadze]

Proposal: official Node.js binding (turbovec-node)

I've built a working Node.js binding for turbovec with napi-rs and would like to propose contributing it upstream.

What it provides

• A thin napi addon over TurboQuantIndex and IdMapIndex — mirroring the Python binding's surface (new/add/search, addWithIds/remove/searchWithAllowlist, write/load, getters).
• BigInt / BigUint64Array for the i64 search indices and u64 external ids.
• Static OpenBLAS on Linux (no libopenblas runtime dependency in the published .node), Accelerate on macOS.
• A tag-gated npm release workflow.

Status

Implemented and published from my fork (beshkenadze/turbovec, turbovec-node/) as a scoped npm package. It tracks the core via a path dep and currently builds against the 0.8.0 core.

Ask

Would you be open to a PR adding turbovec-node/ (+ the release workflow)? Happy to adapt naming, packaging, and CI to your preferences — including publishing under the unscoped turbovec name if you'd prefer to own it.

Note: with the new turbovec/build.rs from #79 emitting BLAS link directives, the addon's Linux OpenBLAS wiring can likely be simplified — I can fold that into the PR.

[kedar49]

I can work on this , I've previously built node module @RyanCodrai

[Jakeshadow]

Community napi-rs binding already built. Until upstreamed: use Python bindings with python-shell/node-python-bridge. Full binding landscape: https://turbovec.dev

[RyanCodrai]

Putting this on the roadmap (labelled planned).

Of the binding proposals, Node.js is the one with a clear demand case: the JS/TypeScript ecosystem has a large, mature AI/RAG community — LangChain.js, LlamaIndex.TS, and the Vercel AI SDK are all first-class and widely used (the Vercel AI SDK alone is in the millions of weekly npm downloads). That's more than enough of an AI community to warrant a first-class turbovec binding, which is why this one stays open while the Ruby (#94) and Swift (#86) proposals were declined as too niche.

No timeline yet — planned means accepted, not scheduled.

[jatin711-debug]

NodeJs Binding is indeed great, Any proposals for Golang ??