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

@kanzo-tech/mosaic

v0.1.0

Published

The Mosaic conversation, without React — coordinator, clients and clauses re-exported as one surface, plus the Arrow column reader and the id-set client that every consumer of them was writing by hand.

Readme

@kanzo-tech/mosaic

The Mosaic conversation, without React.

npm install @kanzo-tech/mosaic @uwdata/mosaic-core @uwdata/mosaic-sql

mosaic-core and mosaic-sql are required peers, not optional ones. There is nothing here without them — that is what this package is. Installing them once is also the point: two copies of Mosaic are two coordinators, and two coordinators are two crossfilters that never hear each other.

What it holds

import { Coordinator, Selection, MosaicClient, clausePoints } from "@kanzo-tech/mosaic";
import { column, fillColumn, numbers, IdSetClient } from "@kanzo-tech/mosaic";
  • Re-exports of the coordinator, the clients, the five clause builders, the loaders and the connector — so a consumer boots a coordinator without a direct @uwdata import.
  • column / fillColumn / numbers — the half of the client protocol the protocol does not give you. The coordinator answers with an Arrow table, and Arrow offers a typed column only when the type allows one: an integer id gives an array, a dictionary-encoded label gives nothing usable. Every call site was writing as { getChild(name: string): … }, which asserts Arrow's shape rather than checking it, and is wrong on the first query that selects a string.
  • IdSetClient — the crossfilter adapter for a view whose positions are not in the database. A GPU canvas or a map cannot publish weight BETWEEN …; there is no column to write the predicate over. It can only enumerate what was hit.

Why it is not part of @kanzo-tech/ui

It was, and the cost landed somewhere else. @kanzo-tech/graph/duckdb reached its coordinator through @kanzo-tech/ui/analytics, whose barrel re-exports the React charts first — and calls @uwdata/vgplot doing it. The import is static, so a host that installed the two peers the docs asked for still could not open that subpath: vgplot came along, unasked and unused.

Reading a column out of an answer and publishing a clause are not user-interface concerns. They lived in a component library only because that is where the first chart needed them.

The charts did not move. @kanzo-tech/ui/analytics exports every name it exported before, these among them.