@lotics/ui 27.10.0 → 27.11.0

package/AGENTS.md

@@ -14,7 +14,7 @@ CURRENT major only — upgrading an app across majors is `MIGRATION.md`.
 
 | Doc | Read it for |
 |---|---|
-| [docs/catalog.md](./docs/catalog.md) | **The complete inventory** — Reach-by-role (each data role → the ONE canonical component) + every `@lotics/ui/<module>` entry point (incl. `@lotics/ui/vite`'s `loticsOptimizeDeps` for a custom-code app's `vite.config.ts`). Read before building any screen; reuse first. |
+| [docs/catalog.md](./docs/catalog.md) | **The complete inventory** — Reach-by-role (each data role → the ONE canonical component) + every `@lotics/ui/<module>` entry point (incl. `@lotics/ui/vite`'s `loticsOptimizeDeps` + `loticsResolve()` — the pre-bundle list and the whole `resolve` block a custom-code app's `vite.config.ts` imports rather than hand-carries, dev-link included). Read before building any screen; reuse first. |
 | [docs/data_entry.md](./docs/data_entry.md) | Which editing pattern for which job — inline edit, fieldset forms, browser-autofill suppression (search controls only), find-or-create (`Combobox`), line items, handoffs, phased records, billing, tags, dispositions, attachments (the `FilesEditor` COMPOUND — root owns selection/gallery/confirm, you compose the bar, a HOST verb reads `useFilesEditorSelection` — plus the three-way file INTAKE: CTA + `FileDropTarget` + `usePasteFiles`), stage gates, the commit-on-blur vs action-press ordering law (the kit gates the press — `pending_commits`). |
 | [docs/ai_patterns.md](./docs/ai_patterns.md) | AI acts, the human stays in charge — composer, live run feed (`AgentRun`), the one law's split (modify → review-before-apply; create → save-direct + the `ResultHeader` receipt), findings, provenance, confidence; the UI half of the SDK's [ai doc](../app-sdk/docs/ai.md)., the whole run in a dialog (`AgentRunScope`/`AgentRunPane`/`AgentRunActions` — a parked question REPLACES the feed, actions in the footer) |
 | [docs/composition.md](./docs/composition.md) | The design-language contract — canvas + content column, heading altitude (incl. eyebrow vs group lead — a label is one or the other), banded cards, register vs inset rows, master-detail `Drawer` on a LIST screen vs a child collection's row EXPANDING inside a record, view controls, RECORD EXTENT (one page, sections scrolled to and never routed to), color discipline, typography, whitespace, and how to TEST an overlay component (a `Popover`-backed surface never mounts under jsdom). |

package/docs/catalog.md

@@ -325,6 +325,18 @@ source (`src/<module>.tsx`/`.ts`) is the API reference.
   `import { loticsOptimizeDeps } from "@lotics/ui/vite"` → `optimizeDeps: { include: loticsOptimizeDeps }`.
   To add app-specific entries, spread: `include: [...loticsOptimizeDeps, "my-dep"]`. A Node-loadable
   `.mjs` leaf (a Vite config can't import a `.ts` from `node_modules`), zero-import by contract.
+- **`vite`** — `loticsResolve()`: the whole `resolve` block, for the same reason and on the same
+  terms — `resolve: loticsResolve()`. Every entry is dictated by the kit's internals, so the kit
+  owns them: the `react-native` → `react-native-web` alias (**load-bearing** — without it the RN
+  primitives have no web implementation and the app does not build), `.web.tsx`-first `extensions`
+  (per-target variants win; `.mjs`/`.mts` kept for parity with Vite's default resolver), `dedupe`
+  for React + RN-Web (the kit is consumed across many subpaths, and a second React copy in one
+  chunk nulls the hooks dispatcher — "Invalid hook call"), and the `LOTICS_UI_SRC` **dev-link**,
+  read at call time so it lasts exactly one command. To add your own alias, spread:
+  `const base = loticsResolve(); resolve: { ...base, alias: [...base.alias, entry] }`.
+  `lotics app codegen` writes the matching `paths` into the app's `.lotics/tsconfig.link.json`,
+  so `tsc`, vitest, eslint and the editor resolve the same kit Vite does — the dev-link is not a
+  Vite-only trick that leaves every other tool checking the published package.
 
 ### Text & formatting
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/ui",
-  "version": "27.10.0",
+  "version": "27.11.0",
   "type": "module",
   "exports": {
     "./vite": {

package/src/react_native.d.ts

@@ -4,11 +4,14 @@ import "react-native";
 // Pressable's `hovered` callback state, plus web-only ViewStyle / TextStyle
 // properties (cursor, outline, boxShadow, etc.) used by its primitives.
 //
-// Each consumer (frontend, container-invoices, future iframe
-// apps) ships its own copy of this file in its `src/`. TypeScript doesn't
-// auto-pick-up `.d.ts` files inside node_modules dependencies; the augmentation
-// has to be visible in the consumer's `include`. The CLI starter template
-// (`lotics app create`) generates this file as part of every new app.
+// TypeScript does not auto-load a `.d.ts` from inside a dependency — the
+// augmentation has to be visible in the consumer's own `include`. In-repo
+// consumers (frontend) keep a copy in `src/`; a custom-code app does NOT, because
+// `lotics app codegen` copies THIS file into its `.lotics/` on every run. That
+// direction matters: a scaffolded snapshot silently falls behind whatever the kit
+// adds here — the starter's copy was already missing `TextStyle`'s `boxShadow`,
+// `transitionDuration` and `transitionProperty`, so an app author writing one got
+// a type error the kit itself does not have.
 declare module "react-native" {
   interface PressableStateCallbackType {
     hovered: boolean;

package/src/vite.d.mts

@@ -5,3 +5,13 @@
  * extend: `include: [...loticsOptimizeDeps, "my-extra-dep"]`.
  */
 export declare const loticsOptimizeDeps: readonly string[];
+
+/**
+ * The Vite `resolve` block for a Lotics custom-code app (runtime in `vite.mjs`).
+ * Reads `LOTICS_UI_SRC` at call time, so the dev-link is decided per command.
+ */
+export declare function loticsResolve(): {
+  alias: ({ find: RegExp; replacement: string } | { find: string; replacement: string })[];
+  extensions: string[];
+  dedupe: string[];
+};

package/src/vite.mjs

@@ -71,3 +71,45 @@ export const loticsOptimizeDeps = [
   "fast-formula-parser",
   "@formulajs/formulajs",
 ];
+
+/**
+ * The complete Vite `resolve` block a Lotics custom-code app needs — the second
+ * half of the same contract `loticsOptimizeDeps` carries, and shipped here for
+ * the same reason: it tracks the installed @lotics/ui and cannot drift.
+ *
+ * Everything in it exists because the kit ships RN-Web SOURCE:
+ *  - the `react-native` → `react-native-web` alias, so the kit's RN primitives
+ *    (View/Text/Pressable/StyleSheet) render on the web at all. This entry is
+ *    LOAD-BEARING: the deleted `lotics ui link` edited it by regex and twice
+ *    deleted it along with the array's closing bracket (GAP-133/142), which is
+ *    why the dev-link below is computed here rather than written into an app.
+ *  - `.web.tsx`-first `extensions`, so per-target variants (avatar.web.tsx) win,
+ *    plus `.mjs`/`.mts` to keep parity with Vite's default resolver — an override
+ *    otherwise drops them and a package shipping only `.mjs` (lucide-react/dynamic,
+ *    reached by DynamicIcon/AppIcon) fails to resolve under `lotics app dev` while
+ *    the prod build resolves it, so the gap is dev-only and silent.
+ *  - `dedupe`, because the kit is consumed across many subpath entries and Vite
+ *    can otherwise pre-bundle one into its own chunk with a second React copy —
+ *    a hook called from there hits a null dispatcher ("Invalid hook call").
+ *  - the `LOTICS_UI_SRC` dev-link, when set: kit edits go live under
+ *    `lotics app dev` (HMR) and bundle under `lotics app deploy`, with no publish
+ *    round-trip. `lotics app codegen` writes the matching `paths` into
+ *    `.lotics/tsconfig.link.json` from the same variable, so `tsc`, vitest, eslint
+ *    and the editor resolve the same copy Vite does — the dev-link is not a
+ *    Vite-only trick that lies to every other tool.
+ *
+ * An app that needs its own alias spreads the result:
+ *   const base = loticsResolve();
+ *   resolve: { ...base, alias: [...base.alias, { find: "x", replacement: "y" }] }
+ */
+export function loticsResolve() {
+  const uiSrc = process.env.LOTICS_UI_SRC;
+  return {
+    alias: [
+      ...(uiSrc ? [{ find: /^@lotics\/ui\/(.+)$/, replacement: `${uiSrc}/$1` }] : []),
+      { find: "react-native", replacement: "react-native-web" },
+    ],
+    extensions: [".web.tsx", ".web.ts", ".web.js", ".tsx", ".ts", ".jsx", ".js", ".mjs", ".mts"],
+    dedupe: ["react", "react-dom", "react-native-web"],
+  };
+}