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

@sqlrooms/duckdb-node

v0.29.0

Published

Node.js DuckDB connector for SQLRooms, based on [@duckdb/node-api](https://duckdb.org/docs/stable/clients/node_neo/overview).

Readme

Node.js DuckDB connector for SQLRooms, based on @duckdb/node-api.

Installation

pnpm add @sqlrooms/duckdb-node

Usage

import {createNodeDuckDbConnector} from '@sqlrooms/duckdb-node';

// Create connector
const connector = createNodeDuckDbConnector({
  dbPath: ':memory:',
  initializationQuery: 'INSTALL json; LOAD json;',
});

// Initialize
await connector.initialize();

// Execute queries
await connector.execute('CREATE TABLE users (id INTEGER, name VARCHAR)');

// Query with Arrow result
const table = await connector.query('SELECT * FROM users');
console.log(table.numRows);

// Query with JSON result
const users = await connector.queryJson('SELECT * FROM users');
for (const user of users) {
  console.log(user);
}

// Clean up
await connector.destroy();

Arrow result types

The connector installs and loads DuckDB's nanoarrow community extension during initialization, then uses DuckDB's own Arrow IPC conversion for query results. Initialization fails if the extension cannot be installed or loaded. CI and other restricted-network environments should make the extension available in DuckDB's extension cache before creating the connector.

Returned Arrow values follow DuckDB's declared types instead of inferred JavaScript types. For example, BIGINT values are Arrow Int64 values exposed as JavaScript bigint, DATE remains Date32, and BLOB remains Binary. Callers that serialize query results must handle values such as bigint explicitly.

API

createNodeDuckDbConnector(options?)

Creates a new Node.js DuckDB connector.

Options:

  • dbPath - Path to database file or :memory: (default: :memory:)
  • initializationQuery - SQL to run after initialization
  • config - DuckDB configuration options

Returns: NodeDuckDbConnector

NodeDuckDbConnector

  • initialize() - Initialize the connector
  • destroy() - Clean up resources
  • execute(sql, options?) - Execute SQL without returning results
  • query(sql, options?) - Execute SQL and return Arrow table
  • queryJson(sql, options?) - Execute SQL and return JSON objects
  • getInstance() - Get underlying DuckDB instance
  • getConnection() - Get underlying DuckDB connection