@kanzo-tech/mosaic 0.14.0 → 0.15.1

package/README.md

@@ -14,7 +14,7 @@ Mosaic are two coordinators, and two coordinators are two crossfilters that neve
 
 ```ts
 import { Coordinator, Selection, MosaicClient, clausePoints } from "@kanzo-tech/mosaic";
-import { column, fillColumn, numbers } from "@kanzo-tech/mosaic";
+import { column, numbers } from "@kanzo-tech/mosaic";
 import { engine } from "@kanzo-tech/mosaic";
 ```
 
@@ -47,7 +47,7 @@ import { engine } from "@kanzo-tech/mosaic";
 - **Re-exports** of the coordinator, the clients, the five clause builders and the loaders — so a
   consumer never needs a direct `@uwdata` import. The DuckDB-WASM connector is not among them:
   `engine()` is the only boot.
-- **`column` / `fillColumn` / `numbers`** — the half of the client protocol the protocol does not
+- **`column` / `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
@@ -58,13 +58,10 @@ import { engine } from "@kanzo-tech/mosaic";
 
 ## 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, and the
+consumers that need them are not all charts. `@kanzo-tech/graph` depends on this package and not on
+`@kanzo-tech/ui/analytics`, whose barrel imports `@uwdata/vgplot` statically: a host that draws a
+graph and no chart installs no vgplot.
 
-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`](https://kanzo-tech.github.io/ui) exports
-every name it exported before, these among them.
+`@kanzo-tech/ui/analytics` keeps the charts and re-exports these names, so a chart consumer imports
+from one place.

package/dist/arrow.d.ts

@@ -16,22 +16,4 @@
 export declare function column(data: unknown, field: string): unknown[];
 /** The same, coerced — Arrow hands back `BigInt` for some integer widths. */
 export declare function numbers(data: unknown, field: string): number[];
-/** A pre-sized destination `fillColumn` can write into. */
-export type NumericArray = Float32Array | Float64Array | Uint32Array | Uint16Array | Int32Array;
-/**
- * One numeric column, written straight into a typed array the caller already owns.
- *
- * `numbers()` is the wrong tool once a result is large: `toArray()` already hands back a typed
- * buffer, and `Array.from(...).map(Number)` turns it into two full-length boxed `number[]` on the
- * way to a third array that was the actual destination. Three allocations to move nothing. This is
- * the same pass with none of them — which is what lets a caller size once against its own limit and
- * fill from the Arrow batches as they arrive.
- *
- * `stride` and `offset` are how interleaving is expressed: `x` at `(0, 2)` and `y` at `(1, 2)` fill
- * one `[x0, y0, x1, y1, …]` buffer with no seam between them.
- *
- * Returns how many rows were written, which is `min(rows, capacity)` — a caller that sized against
- * a `LIMIT` uses it to `subarray` down to what actually came back.
- */
-export declare function fillColumn(data: unknown, field: string, into: NumericArray, offset?: number, stride?: number): number;
 //# sourceMappingURL=arrow.d.ts.map

package/dist/arrow.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"arrow.d.ts","sourceRoot":"","sources":["../src/arrow.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAMH,4CAA4C;AAC5C,wBAAgB,MAAM,CAAC,IAAI,EAAE,OAAO,EAAE,KAAK,EAAE,MAAM,GAAG,OAAO,EAAE,CAI9D;AAED,6EAA6E;AAC7E,wBAAgB,OAAO,CAAC,IAAI,EAAE,OAAO,EAAE,KAAK,EAAE,MAAM,GAAG,MAAM,EAAE,CAE9D;AAED,2DAA2D;AAC3D,MAAM,MAAM,YAAY,GAAG,YAAY,GAAG,YAAY,GAAG,WAAW,GAAG,WAAW,GAAG,UAAU,CAAC;AAEhG;;;;;;;;;;;;;;GAcG;AACH,wBAAgB,UAAU,CACxB,IAAI,EAAE,OAAO,EACb,KAAK,EAAE,MAAM,EACb,IAAI,EAAE,YAAY,EAClB,MAAM,SAAI,EACV,MAAM,SAAI,GACT,MAAM,CAiBR"}
+{"version":3,"file":"arrow.d.ts","sourceRoot":"","sources":["../src/arrow.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAMH,4CAA4C;AAC5C,wBAAgB,MAAM,CAAC,IAAI,EAAE,OAAO,EAAE,KAAK,EAAE,MAAM,GAAG,OAAO,EAAE,CAI9D;AAED,6EAA6E;AAC7E,wBAAgB,OAAO,CAAC,IAAI,EAAE,OAAO,EAAE,KAAK,EAAE,MAAM,GAAG,MAAM,EAAE,CAE9D"}

package/dist/arrow.js

@@ -23,39 +23,4 @@ export function column(data, field) {
 export function numbers(data, field) {
     return column(data, field).map(Number);
 }
-/**
- * One numeric column, written straight into a typed array the caller already owns.
- *
- * `numbers()` is the wrong tool once a result is large: `toArray()` already hands back a typed
- * buffer, and `Array.from(...).map(Number)` turns it into two full-length boxed `number[]` on the
- * way to a third array that was the actual destination. Three allocations to move nothing. This is
- * the same pass with none of them — which is what lets a caller size once against its own limit and
- * fill from the Arrow batches as they arrive.
- *
- * `stride` and `offset` are how interleaving is expressed: `x` at `(0, 2)` and `y` at `(1, 2)` fill
- * one `[x0, y0, x1, y1, …]` buffer with no seam between them.
- *
- * Returns how many rows were written, which is `min(rows, capacity)` — a caller that sized against
- * a `LIMIT` uses it to `subarray` down to what actually came back.
- */
-export function fillColumn(data, field, into, offset = 0, stride = 1) {
-    const capacity = Math.max(0, Math.ceil((into.length - offset) / stride));
-    const values = data.getChild?.(field)?.toArray();
-    if (values) {
-        const n = Math.min(values.length, capacity);
-        // `Number` is identity on the numeric widths and the conversion on the BigInt ones; either way
-        // it reads an element rather than allocating one.
-        for (let i = 0; i < n; i++)
-            into[offset + i * stride] = Number(values[i]);
-        return n;
-    }
-    let i = 0;
-    for (const row of data) {
-        if (i >= capacity)
-            break;
-        into[offset + i * stride] = Number(row[field]);
-        i++;
-    }
-    return i;
-}
 //# sourceMappingURL=arrow.js.map

package/dist/arrow.js.map

@@ -1 +1 @@
-{"version":3,"file":"arrow.js","sourceRoot":"","sources":["../src/arrow.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAMH,4CAA4C;AAC5C,MAAM,UAAU,MAAM,CAAC,IAAa,EAAE,KAAa;IACjD,MAAM,KAAK,GAAI,IAAkB,CAAC,QAAQ,EAAE,CAAC,KAAK,CAAC,CAAC;IACpD,IAAI,KAAK;QAAE,OAAO,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,OAAO,EAAE,CAAC,CAAC;IAC9C,OAAO,KAAK,CAAC,IAAI,CAAC,IAAyC,EAAE,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC,CAAC;AACpF,CAAC;AAED,6EAA6E;AAC7E,MAAM,UAAU,OAAO,CAAC,IAAa,EAAE,KAAa;IAClD,OAAO,MAAM,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC;AACzC,CAAC;AAKD;;;;;;;;;;;;;;GAcG;AACH,MAAM,UAAU,UAAU,CACxB,IAAa,EACb,KAAa,EACb,IAAkB,EAClB,MAAM,GAAG,CAAC,EACV,MAAM,GAAG,CAAC;IAEV,MAAM,QAAQ,GAAG,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,IAAI,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,MAAM,GAAG,MAAM,CAAC,GAAG,MAAM,CAAC,CAAC,CAAC;IACzE,MAAM,MAAM,GAAI,IAAkB,CAAC,QAAQ,EAAE,CAAC,KAAK,CAAC,EAAE,OAAO,EAAE,CAAC;IAChE,IAAI,MAAM,EAAE,CAAC;QACX,MAAM,CAAC,GAAG,IAAI,CAAC,GAAG,CAAC,MAAM,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC;QAC5C,+FAA+F;QAC/F,kDAAkD;QAClD,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,CAAC,EAAE,CAAC,EAAE;YAAE,IAAI,CAAC,MAAM,GAAG,CAAC,GAAG,MAAM,CAAC,GAAG,MAAM,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC;QAC1E,OAAO,CAAC,CAAC;IACX,CAAC;IACD,IAAI,CAAC,GAAG,CAAC,CAAC;IACV,KAAK,MAAM,GAAG,IAAI,IAAyC,EAAE,CAAC;QAC5D,IAAI,CAAC,IAAI,QAAQ;YAAE,MAAM;QACzB,IAAI,CAAC,MAAM,GAAG,CAAC,GAAG,MAAM,CAAC,GAAG,MAAM,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC,CAAC;QAC/C,CAAC,EAAE,CAAC;IACN,CAAC;IACD,OAAO,CAAC,CAAC;AACX,CAAC"}
+{"version":3,"file":"arrow.js","sourceRoot":"","sources":["../src/arrow.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAMH,4CAA4C;AAC5C,MAAM,UAAU,MAAM,CAAC,IAAa,EAAE,KAAa;IACjD,MAAM,KAAK,GAAI,IAAkB,CAAC,QAAQ,EAAE,CAAC,KAAK,CAAC,CAAC;IACpD,IAAI,KAAK;QAAE,OAAO,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,OAAO,EAAE,CAAC,CAAC;IAC9C,OAAO,KAAK,CAAC,IAAI,CAAC,IAAyC,EAAE,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC,CAAC;AACpF,CAAC;AAED,6EAA6E;AAC7E,MAAM,UAAU,OAAO,CAAC,IAAa,EAAE,KAAa;IAClD,OAAO,MAAM,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC;AACzC,CAAC"}

package/dist/index.d.ts

@@ -1,29 +1,18 @@
 /**
- * The Mosaic conversation, as one import.
+ * The Mosaic conversation, as one import, with no React in it.
  *
- * This package exists because of a bug that shipped. `@kanzo-tech/graph/duckdb` reached its
- * coordinator, clients and clauses through `@kanzo-tech/ui/analytics`, whose barrel re-exports the
- * React charts first — and `@uwdata/vgplot` with them. The import is static, so a host that
- * installed the two peers the documentation asked for, `mosaic-core` and `mosaic-sql`, still could
- * not open the subpath: vgplot came along, unasked and unused. `@kanzo-tech/graph` ended up
- * declaring vgplot as an optional peer to paper over a dependency it never names.
+ * Reading a column out of an Arrow answer and publishing a clause are not user-interface concerns,
+ * so they live here and both `@kanzo-tech/graph` and `@kanzo-tech/ui/analytics` depend on this
+ * rather than on each other; the graph never pulls in vgplot. `@kanzo-tech/ui/analytics` re-exports
+ * these names.
  *
- * The cause was a layer in the wrong package rather than a missing entry in a list. Reading a
- * column out of an Arrow answer and publishing a points clause are not user-interface concerns;
- * they were only in a component library because that is where the first chart needed them.
- *
- * So: the data half lives here, with no React anywhere in it, and both consumers depend on this
- * rather than on each other. `@kanzo-tech/ui/analytics` keeps every chart and re-exports these
- * names unchanged, so nothing on that surface moves.
- *
- * The re-exports below are deliberate rather than lazy. A single import site for `Coordinator` and
- * `Selection` is what makes one copy of Mosaic the easy outcome, and two copies would be two
- * crossfilters that never hear each other.
+ * The re-exports are deliberate: one import site for `Coordinator` and `Selection` makes one copy
+ * of Mosaic the easy outcome, and two copies would be two crossfilters that never hear each other.
  */
 export { Coordinator, MosaicClient, Selection, makeClient, clausePoint, clausePoints, clauseInterval, clauseIntervals, clauseMatch, type SelectionClause, } from "@uwdata/mosaic-core";
 export { Query, asc, desc, loadCSV, loadJSON, loadObjects, loadParquet, loadSpatial, loadExtension, type ExprValue, type FilterExpr, } from "@uwdata/mosaic-sql";
 /** Ours: turning an Arrow answer into values, which the client protocol does not do for you. */
-export { column, fillColumn, numbers, type NumericArray } from "./arrow.js";
+export { column, numbers } from "./arrow.js";
 /** Ours: what every `table` here and in the charts takes — one identifier, or a relation named in SQL. */
 export { type TableExpr } from "./table.js";
 /**

package/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AAEH,OAAO,EACL,WAAW,EACX,YAAY,EACZ,SAAS,EACT,UAAU,EACV,WAAW,EACX,YAAY,EACZ,cAAc,EACd,eAAe,EACf,WAAW,EACX,KAAK,eAAe,GACrB,MAAM,qBAAqB,CAAC;AAE7B,OAAO,EACL,KAAK,EACL,GAAG,EACH,IAAI,EACJ,OAAO,EACP,QAAQ,EACR,WAAW,EACX,WAAW,EACX,WAAW,EACX,aAAa,EACb,KAAK,SAAS,EACd,KAAK,UAAU,GAChB,MAAM,oBAAoB,CAAC;AAE5B,gGAAgG;AAChG,OAAO,EAAE,MAAM,EAAE,UAAU,EAAE,OAAO,EAAE,KAAK,YAAY,EAAE,MAAM,YAAY,CAAC;AAE5E,0GAA0G;AAC1G,OAAO,EAAE,KAAK,SAAS,EAAE,MAAM,YAAY,CAAC;AAE5C;;;;GAIG;AACH,OAAO,EAAE,MAAM,EAAE,KAAK,MAAM,EAAE,MAAM,aAAa,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,OAAO,EACL,WAAW,EACX,YAAY,EACZ,SAAS,EACT,UAAU,EACV,WAAW,EACX,YAAY,EACZ,cAAc,EACd,eAAe,EACf,WAAW,EACX,KAAK,eAAe,GACrB,MAAM,qBAAqB,CAAC;AAE7B,OAAO,EACL,KAAK,EACL,GAAG,EACH,IAAI,EACJ,OAAO,EACP,QAAQ,EACR,WAAW,EACX,WAAW,EACX,WAAW,EACX,aAAa,EACb,KAAK,SAAS,EACd,KAAK,UAAU,GAChB,MAAM,oBAAoB,CAAC;AAE5B,gGAAgG;AAChG,OAAO,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,YAAY,CAAC;AAE7C,0GAA0G;AAC1G,OAAO,EAAE,KAAK,SAAS,EAAE,MAAM,YAAY,CAAC;AAE5C;;;;GAIG;AACH,OAAO,EAAE,MAAM,EAAE,KAAK,MAAM,EAAE,MAAM,aAAa,CAAC"}

package/dist/index.js

@@ -1,29 +1,18 @@
 /**
- * The Mosaic conversation, as one import.
+ * The Mosaic conversation, as one import, with no React in it.
  *
- * This package exists because of a bug that shipped. `@kanzo-tech/graph/duckdb` reached its
- * coordinator, clients and clauses through `@kanzo-tech/ui/analytics`, whose barrel re-exports the
- * React charts first — and `@uwdata/vgplot` with them. The import is static, so a host that
- * installed the two peers the documentation asked for, `mosaic-core` and `mosaic-sql`, still could
- * not open the subpath: vgplot came along, unasked and unused. `@kanzo-tech/graph` ended up
- * declaring vgplot as an optional peer to paper over a dependency it never names.
+ * Reading a column out of an Arrow answer and publishing a clause are not user-interface concerns,
+ * so they live here and both `@kanzo-tech/graph` and `@kanzo-tech/ui/analytics` depend on this
+ * rather than on each other; the graph never pulls in vgplot. `@kanzo-tech/ui/analytics` re-exports
+ * these names.
  *
- * The cause was a layer in the wrong package rather than a missing entry in a list. Reading a
- * column out of an Arrow answer and publishing a points clause are not user-interface concerns;
- * they were only in a component library because that is where the first chart needed them.
- *
- * So: the data half lives here, with no React anywhere in it, and both consumers depend on this
- * rather than on each other. `@kanzo-tech/ui/analytics` keeps every chart and re-exports these
- * names unchanged, so nothing on that surface moves.
- *
- * The re-exports below are deliberate rather than lazy. A single import site for `Coordinator` and
- * `Selection` is what makes one copy of Mosaic the easy outcome, and two copies would be two
- * crossfilters that never hear each other.
+ * The re-exports are deliberate: one import site for `Coordinator` and `Selection` makes one copy
+ * of Mosaic the easy outcome, and two copies would be two crossfilters that never hear each other.
  */
 export { Coordinator, MosaicClient, Selection, makeClient, clausePoint, clausePoints, clauseInterval, clauseIntervals, clauseMatch, } from "@uwdata/mosaic-core";
 export { Query, asc, desc, loadCSV, loadJSON, loadObjects, loadParquet, loadSpatial, loadExtension, } from "@uwdata/mosaic-sql";
 /** Ours: turning an Arrow answer into values, which the client protocol does not do for you. */
-export { column, fillColumn, numbers } from "./arrow.js";
+export { column, numbers } from "./arrow.js";
 /** Ours: what every `table` here and in the charts takes — one identifier, or a relation named in SQL. */
 export {} from "./table.js";
 /**

package/dist/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AAEH,OAAO,EACL,WAAW,EACX,YAAY,EACZ,SAAS,EACT,UAAU,EACV,WAAW,EACX,YAAY,EACZ,cAAc,EACd,eAAe,EACf,WAAW,GAEZ,MAAM,qBAAqB,CAAC;AAE7B,OAAO,EACL,KAAK,EACL,GAAG,EACH,IAAI,EACJ,OAAO,EACP,QAAQ,EACR,WAAW,EACX,WAAW,EACX,WAAW,EACX,aAAa,GAGd,MAAM,oBAAoB,CAAC;AAE5B,gGAAgG;AAChG,OAAO,EAAE,MAAM,EAAE,UAAU,EAAE,OAAO,EAAqB,MAAM,YAAY,CAAC;AAE5E,0GAA0G;AAC1G,OAAO,EAAkB,MAAM,YAAY,CAAC;AAE5C;;;;GAIG;AACH,OAAO,EAAE,MAAM,EAAe,MAAM,aAAa,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,OAAO,EACL,WAAW,EACX,YAAY,EACZ,SAAS,EACT,UAAU,EACV,WAAW,EACX,YAAY,EACZ,cAAc,EACd,eAAe,EACf,WAAW,GAEZ,MAAM,qBAAqB,CAAC;AAE7B,OAAO,EACL,KAAK,EACL,GAAG,EACH,IAAI,EACJ,OAAO,EACP,QAAQ,EACR,WAAW,EACX,WAAW,EACX,WAAW,EACX,aAAa,GAGd,MAAM,oBAAoB,CAAC;AAE5B,gGAAgG;AAChG,OAAO,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,YAAY,CAAC;AAE7C,0GAA0G;AAC1G,OAAO,EAAkB,MAAM,YAAY,CAAC;AAE5C;;;;GAIG;AACH,OAAO,EAAE,MAAM,EAAe,MAAM,aAAa,CAAC"}

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@kanzo-tech/mosaic",
-  "version": "0.14.0",
-  "description": "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.",
+  "version": "0.15.1",
+  "description": "The Mosaic conversation, without React — coordinator, clients and clauses re-exported as one surface, plus the Arrow column reader and the page's one DuckDB-WASM engine.",
   "type": "module",
   "license": "MIT",
   "sideEffects": false,