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

lakeql

v0.1.7

Published

lakeql: lightweight TypeScript query engine for Iceberg + Parquet on object storage

Readme

lakeql

npm license

Query Parquet and Iceberg tables directly from object storage, in TypeScript.

lakeql is small and dependency-light enough to run in Cloudflare Workers and other edge/serverless runtimes, where DuckDB-WASM or a JVM engine is too heavy. It streams with HTTP range reads and bounded memory, and either reads a table correctly or rejects it with a typed error — it won't return quietly-wrong rows.

Try it live in your browser: https://lakeql.com/

npm install lakeql

Quick start

Read a Parquet file over HTTP — no credentials, runs in Node or on the edge:

import { createLake, httpStore, gt } from "lakeql/node";

const lake = createLake({ store: httpStore({ baseUrl: "https://example.com/data" }) });

const rows = await lake
  .path("sales.parquet")
  .select(["store_id", "amount"])
  .where(gt("amount", 100))
  .limit(100)
  .toArray();

Inside a Cloudflare Worker, reading from R2:

import { createLake, r2Store } from "lakeql/cloudflare";

export default {
  async fetch(_req: Request, env: { DATA: R2Bucket }) {
    const lake = createLake({
      store: r2Store(env.DATA),
      budget: { maxOutputRows: 1000, maxConcurrentReads: 4 },
    });
    const rows = await lake.path("sales.parquet").limit(100).toArray();
    return Response.json(rows);
  },
};

Plan an Iceberg table (snapshot selection, partition- and delete-aware pruning):

import { loadIcebergTable, eq } from "lakeql/node";

const table = await loadIcebergTable({
  store: httpStore({ baseUrl: "https://example.com/warehouse" }),
  metadataPath: "places/metadata/v2.metadata.json",
});

const plan = table.planFiles({ ref: "main", where: eq("country", "US") });

Entry points

| Import | Adds | | --- | --- | | lakeql | Core query engine, Parquet, Iceberg, and the unified loadTable / planFiles / scanRows / scanBatches helpers. | | lakeql/node | Everything in lakeql, plus httpStore and s3Store. | | lakeql/cloudflare | Everything in lakeql, plus r2Store. |

CLI

A global install adds a lakeql command for quick local queries:

npm install -g lakeql
lakeql query --path sales.parquet --sql "select region, sum(amount) as revenue from input group by region order by revenue desc"

What it supports

lakeql aims to read supported Parquet and Iceberg features correctly and reject unsupported table semantics explicitly. See the compatibility matrix and unsupported-but-detected. Object-store adapters (httpStore, s3Store, r2Store) use HTTP range reads by default; Iceberg writes are append-only.

Documentation

Full docs, recipes, and the engine contract live in the repository: querying Parquet · querying Iceberg · Cloudflare Workers · error codes · why not DuckDB-WASM?

License

MIT