@uniflowed/ui 0.10.0 → 0.11.1

package/index.js

@@ -99,7 +99,7 @@
 // `InputOtp.Separator`, `Tooltip.Trigger`, `Tooltip.Body`,
 // `HoverCard.Trigger`, `HoverCard.Body` and `Sidebar.Item`. A documented
 // escape hatch that is not there is worse than an undocumented one that is, so
-// the state of every part is a table in `packages/ui/ui.test.js` rather than a
+// the state of every part is a table in `npm/ui/ui.test.js` rather than a
 // claim in this paragraph: it names each part as implemented, no-element, or
 // fixed remainder, and the suite holds the lists to the exported files. A part
 // added to this barrel is in none of them and the suite says so.
@@ -121,7 +121,7 @@
 // that is still checked.
 //
 // **What the CLI adds.** `uf ui add`, `uf ui list` and `uf ui diff`, over a
-// registry of styled components in `registry/ui/` that is embedded into the
+// registry of styled components in `npm/ui/registry/` that is embedded into the
 // binary — each one built on parts exported here, and none of them a copy of
 // one. There is still no registry of *primitives*, for the reason the previous
 // paragraph gives, and there is no `components.json`: `uf.config.js` is the one
@@ -404,7 +404,7 @@ export type { ToggleGroupType } from "./toggle-group.js";
  * Each takes `render`, so the control or line a design system already has — a
  * `<div>` with a knob drawn in it, somebody's `<Pressable>`, a presentational
  * meter shell — keeps the role, state, keys and attributes while being their
- * element. See the module headers and the table in `packages/ui/ui.test.js`.
+ * element. See the module headers and the table in `npm/ui/ui.test.js`.
  */
 export { Checkbox } from "./checkbox.js";
 export { Progress } from "./progress.js";

package/internal/anchor.js

@@ -52,7 +52,7 @@
 // two different places, and which one a reader gets depends on their browser.
 // Shipping one tier that both engines run is worth more than shipping the
 // faster one to some of them, so this module measures. It is the reason
-// `packages/ui` has no `CSS.supports` in it: there is nothing to branch on.
+// `npm/ui` has no `CSS.supports` in it: there is nothing to branch on.
 //
 // The measuring is kept cheap rather than clever. A placement is computed on
 // open, on a scroll anywhere in the page, on a viewport resize and on a resize

package/internal/date-grid.js

@@ -48,7 +48,7 @@
 // arithmetic is where calendar bugs come from in the first place.
 //
 // The specifier is `@uniflowed/core/temporal` rather than `@uniflowed/temporal`,
-// which is the same object — `packages/temporal/index.js` is a re-export and
+// which is the same object — `npm/temporal/index.js` is a re-export and
 // says so. It has to be that one: `@uniflowed/ui` is published to npm,
 // `@uniflowed/temporal` is not yet (its calendar surface waits on the native
 // runtime), and `tools/ci/publishable.sh` refuses a published package that

package/internal/merge-props.js

@@ -90,7 +90,7 @@ export type Rest = { readonly key?: empty, readonly [string]: mixed };
 /**
  * The escape hatch: a caller's element in place of the part's own.
  *
- * `@uniflowed/ui` has no copy step — `packages/ui/index.js`'s header argues
+ * `@uniflowed/ui` has no copy step — `npm/ui/index.js`'s header argues
  * that at length — and the thing a copy step is *for* is changing the markup. A
  * part that always renders a `<button>` cannot be the link a menu of links
  * needs; a heading fixed at `<h2>` is wrong inside an accordion. This is what

package/internal/range.js

@@ -36,7 +36,7 @@
 // `ArrowRight` adds a step in a left-to-right page and subtracts one in a
 // right-to-left page, because the reader is asking for "further along" and
 // further along is the other way. `isReversed` answers that from the element
-// the key arrived on, which is the answer `packages/ui/index.js` prescribes:
+// the key arrived on, which is the answer `npm/ui/index.js` prescribes:
 // the direction is something the DOM knows, so it is read in an event handler
 // rather than provided through a context a caller has to remember to render.
 //

package/internal/selection.js

@@ -29,7 +29,7 @@
 //
 // A public selection manager would be a second way to build a collection, and
 // the point of this package is that there is one. The collections are the
-// public surface; `packages/ui/index.js` says why the internals stay internal.
+// public surface; `npm/ui/index.js` says why the internals stay internal.
 
 export type SelectionMode = "none" | "single" | "multiple";
 export type SelectionBehavior = "toggle" | "replace";

package/internal/visually-hidden-style.js

@@ -5,7 +5,7 @@
 // Its own module, with no `"use client"`, so a part that renders on the server
 // can import it without importing `visually-hidden.js` — a client module whose
 // every export is a client reference to a Server Component. Internal for the
-// reason `packages/ui/index.js` gives about every module here: the public
+// reason `npm/ui/index.js` gives about every module here: the public
 // answer is `VisuallyHidden`.
 
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniflowed/ui",
-  "version": "0.10.0",
+  "version": "0.11.1",
   "description": "Headless, accessible React components whose composition Flow checks, part of the Unified Toolchain for Flow.",
   "type": "module",
   "license": "MIT",
@@ -8,7 +8,7 @@
   "repository": {
     "type": "git",
     "url": "git+https://github.com/ubugeeei-prod/uf.git",
-    "directory": "packages/ui"
+    "directory": "npm/ui"
   },
   "exports": {
     ".": "./index.js"
@@ -16,13 +16,14 @@
   "files": [
     "*.js",
     "internal",
+    "!registry",
     "!*.test.js"
   ],
   "dependencies": {
-    "@uniflowed/core": "0.10.0",
-    "@uniflowed/hooks": "0.10.0",
-    "@uniflowed/react": "0.10.0",
-    "@uniflowed/state": "0.10.0"
+    "@uniflowed/core": "0.11.1",
+    "@uniflowed/hooks": "0.11.1",
+    "@uniflowed/react": "0.11.1",
+    "@uniflowed/state": "0.11.1"
   },
   "peerDependencies": {
     "react": ">=19"