@lotics/cli 0.90.0 → 0.91.0

package/dist/src/cli.js

@@ -30642,7 +30642,7 @@ import { spawn as spawn2 } from "node:child_process";
 import { tmpdir } from "node:os";
 
 // src/starter_template.ts
-var STARTER_FALLBACK_UI_VERSION = "6.1.0";
+var STARTER_FALLBACK_UI_VERSION = "12.1.0";
 var STARTER_FALLBACK_SDK_VERSION = "0.52.0";
 var STARTER_REACT_NATIVE_VERSION = "0.85.3";
 var VITEST_SETUP_FILENAME = "vitest.setup.ts";
@@ -30795,6 +30795,7 @@ function buildStarterTemplate(args) {
 import { defineConfig } from "vite";
 import type { Plugin } from "vite";
 import react from "@vitejs/plugin-react";
+import { loticsOptimizeDeps } from "@lotics/ui/vite";
 
 // @lotics/ui/icon.tsx deep-imports \`lucide-react-native/dist/esm/icons/<name>\`.
 // lucide-react-native's \`exports\` map lists only "." and "./icons", so a strict
@@ -30855,43 +30856,15 @@ export default defineConfig({
     dedupe: ["react", "react-dom", "react-native-web"],
   },
   optimizeDeps: {
-    // \`react-native-svg\` (used by @lotics/ui's svg charts \u2014 PieChart, LineChart,
-    // Sparkline, RingGauge) ships a named-export entry Vite's dev optimizer won't
-    // resolve unbundled ("does not provide an export named 'parse'"), blanking the
-    // iframe the moment one of those charts renders. Pre-bundling it fixes the
-    // interop. Production build (rollup) resolves it without this \u2014 dev-only.
-    //
-    // react-native-web itself is force-prebundled (folds its core CJS deps like
-    // @react-native/normalize-colors into one interop'd chunk), and the deep
-    // subpaths it reaches via *default* imports (e.g. @react-native-picker's web
-    // <select> build) are each pre-bundled into an ESM shim \u2014 Vite's dev optimizer
-    // otherwise serves them without a synthesized default export ("does not
-    // provide an export named 'default'"), blanking the iframe. (Production/rollup
-    // resolves the interop already, so this is dev-only.)
-    //
-    // \`react-markdown\` (@lotics/ui's Markdown renderer, reached by AgentRun and
-    // any markdown surface) pulls a transitive CJS dep, \`style-to-js\`, whose
-    // default export the dev optimizer won't synthesize unbundled ("does not
-    // provide an export named 'default'") \u2014 blanking the iframe the moment a
-    // markdown component mounts. Pre-bundling react-markdown folds the whole
-    // subtree (incl. style-to-js) into one interop'd chunk. It is a regular dep
-    // of @lotics/ui (hoisted), so it needs no package.json entry here. (The GFM
-    // plugin @lotics/ui composes is pure ESM \u2014 no CJS interop to force.)
-    include: [
-      "react-native-svg",
-      "react-markdown",
-      "react-native-web", "@react-native/normalize-colors",
-      "inline-style-prefixer/lib/createPrefixer",
-      "inline-style-prefixer/lib/plugins/crossFade",
-      "inline-style-prefixer/lib/plugins/imageSet",
-      "inline-style-prefixer/lib/plugins/logical",
-      "inline-style-prefixer/lib/plugins/position",
-      "inline-style-prefixer/lib/plugins/sizing",
-      "inline-style-prefixer/lib/plugins/transition",
-      "postcss-value-parser", "fbjs/lib/invariant", "fbjs/lib/warning",
-      "styleq", "styleq/transform-localize-style",
-      "react", "react-dom", "react-dom/client", "nullthrows",
-    ],
+    // The dev dep-optimizer must pre-bundle @lotics/ui's RN-ecosystem + markdown
+    // CJS-interop deps or \`lotics app dev\` blanks the iframe ("does not provide an
+    // export named 'default'/'parse'"). Dev-ONLY: the prod rollup build resolves the
+    // interop without it, so typecheck/lint/build stay green while the dev iframe
+    // goes blank. The canonical list ships WITH @lotics/ui as \`loticsOptimizeDeps\`
+    // (imported above) so it can never drift from what the kit's transitive deps
+    // require across a major bump \u2014 the per-family rationale lives in that module.
+    // To add app-specific entries, spread: include: [...loticsOptimizeDeps, "my-dep"].
+    include: loticsOptimizeDeps,
     // The dep optimizer pre-bundles deps with a SEPARATE esbuild pass that
     // top-level \`define\` doesn't always reach, so a pre-bundled RN dep can
     // still hit \`__DEV__ is not defined\` under \`lotics app dev\`. Define it

package/docs/knowledge_docs.md

@@ -86,7 +86,9 @@ question without ever loading the rest. Structure your content so it works:
 
 Send only the fields you're changing. Content edits are **diffs**, not a full rewrite: pass an
 `edits` array (replace / insert / append operations) plus the `expected_version` you got from
-`read_knowledge` (optimistic concurrency — a stale version is rejected). Refine structure as you
+`read_knowledge` (optimistic concurrency — a stale version is rejected). Over the CLI, the default
+`read_knowledge` text output omits the version — read `current_version` from `lotics run read_knowledge … --json`.
+Refine structure as you
 learn what users actually ask: add the synonym that failed to match, split the section that was
 too coarse to grep. See `lotics tools update_knowledge` for the edit shape.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/cli",
-  "version": "0.90.0",
+  "version": "0.91.0",
   "description": "Lotics SDK and CLI for AI agents",
   "type": "module",
   "bin": {