@civitai/blocks-react 0.65.1 → 0.65.2

package/README.md

@@ -1143,10 +1143,25 @@ The viewer searches in host chrome; the block only ever sees the one resource it
 picked. DISCOVERY ONLY — the returned `versionId` is re-validated + re-priced
 server-side at estimate/submit.
 
-🔴 **Pass NO `baseModelGroup` by default.** It is an optional FILTER, and the host
-hides every resource outside the family you pass — so a hardcoded ecosystem makes
-the viewer's own valid LoRAs invisible and the picker look empty or broken. Omit
-it and the viewer sees everything of that type.
+🔴 **OMIT `baseModelGroup` BY DEFAULT, and never pass a HARDCODED ecosystem.** It
+is an ecosystem-family FILTER, not a label: the host hides every resource outside
+the family you pass, so a literal ecosystem string makes the viewer's own valid
+LoRAs invisible and the picker look empty or broken. Omit it for an unconstrained
+pick and the viewer sees everything of that type. Pass it ONLY when the block
+already holds a chosen checkpoint the pick has to match, and then DERIVE it from
+that checkpoint (`checkpoint.baseModel`). For stack and matrix apps that pair
+LoRAs with a checkpoint, this is the recommended pattern: a derived family keeps
+incompatible LoRAs out of the picker. This hook is PAGE-ONLY, and a page slot has
+no `context.checkpoint` (that field lives on `ModelSlotContext` alone), so the
+family comes from `BlockResourceInfo.baseModel`, the `baseModel` of a Checkpoint
+a picker returned earlier.
+
+For a complete multi-LoRA app, see
+[`starters/examples/generate-studio`](https://github.com/civitai/civitai-app-starters/tree/main/starters/examples/generate-studio):
+`src/components/ModelSection.tsx` opens the picker once per LoRA slot, up to
+`MAX_LORAS`, with a `baseModelGroup` derived from the selected checkpoint, and
+`keepCompatibleLoras` (`src/studio/setup.ts`) re-filters the stack when the
+checkpoint changes, dropping LoRAs made for another family.
 
 ```tsx
 const { open } = useResourcePicker();
@@ -1157,12 +1172,8 @@ if (picked) {
 }
 ```
 
-Constrain it **only** when the block already holds a chosen checkpoint the pick has
-to match — and then derive the family from that checkpoint, never from a literal.
-🔴 **This hook is PAGE-ONLY, and a page slot has no `context.checkpoint`** — that
-field lives on `ModelSlotContext` alone, so the family comes from
-`BlockResourceInfo.baseModel`, the `baseModel` of a Checkpoint this same picker
-returned earlier:
+Constrained to the family of a checkpoint the block already holds, derived from
+that checkpoint, never from a literal:
 
 ```tsx
 const { open } = useResourcePicker();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@civitai/blocks-react",
-  "version": "0.65.1",
+  "version": "0.65.2",
   "description": "React hooks and iframe transport for Civitai Apps. Pairs with @civitai/app-sdk/blocks.",
   "license": "MIT",
   "type": "module",
@@ -37,8 +37,8 @@
     "node": ">=20"
   },
   "dependencies": {
-    "@civitai/components": "^0.9.3",
-    "@civitai/theme": "^0.5.2"
+    "@civitai/theme": "^0.5.2",
+    "@civitai/components": "^0.9.3"
   },
   "comment-peerDependencies": "This floor is DERIVED, not chosen — the lowest published app-sdk that exports every symbol this package imports. Do not edit it without reading ./PEER_FLOOR.md (in-repo, unpublished) and tests/guards/blocks-react-peer-floor.test.mjs.",
   "peerDependencies": {
@@ -58,7 +58,7 @@
     "typescript": "^5.9.2",
     "vite": "^8.0.14",
     "vitest": "^4.1.11",
-    "@civitai/app-sdk": "^0.59.0"
+    "@civitai/app-sdk": "^0.60.0"
   },
   "publishConfig": {
     "access": "public"