@kanzo-tech/mosaic 0.15.0 → 0.16.0

package/README.md

@@ -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/index.d.ts

@@ -1,24 +1,13 @@
 /**
- * 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";

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,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"}
+{"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,24 +1,13 @@
 /**
- * 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";

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,OAAO,EAAE,MAAM,YAAY,CAAC;AAE7C,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.15.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.16.0",
+  "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,