@synapse-sdk/react 0.3.7 → 0.3.9

package/README.md

@@ -6,6 +6,11 @@ React hooks for a Synapse node: `<SynapseProvider node={node}>` above your compo
 `useSceneStatus(scene)`, `useTasks(select?)` and `useDiscover()` (your clusters, once signed in). Every hook reads a value the node keeps current; none keeps its own
 copy.
 
+`useCatalog().topics` lists every topic that has a publisher or a subscriber that reads it with a schema: each entry
+has the topic's shape (`desc`), its `publishers` and its `subscribers` (`{ name }` per node). A controller waiting for
+commands shows up there before anyone publishes. A subscription by name only, or to a topic defined without a schema,
+is not listed.
+
 ## Two kinds of users
 
 - **Node author** (a robot driver, a sim, a task, a panel that edits a few known things): `node.store(name)` with

package/dist/index.d.ts

@@ -16,7 +16,8 @@ type AuthState = {
  * Makes `node` the node of every hook below. With `useAuth` (Clerk's own `useAuth`, or `fakeAuth(token)`), the person
  * signed in there is the node's (`node.setAuth`): signed in → the node asks the key server with their credential;
  * signed out → `node.setAuth(undefined)`; not known yet → nothing; a different `userId` while signed in → a new sign-in. `useAuth` is a hook: pass it on every render or never.
- * Signing out ends no live session.
+ * Signing out ends no live session. The sign-in is set in a layout effect, so a child's effect on first mount (a
+ * `connect("<runtime>@<cluster>")`) finds it on the node.
  */
 export declare function SynapseProvider({ node, useAuth, children }: {
     node: Synapse;

package/dist/index.js

@@ -3,22 +3,25 @@
 //
 // Statuses speak TanStack here (`idle | pending | success | error`, like `useMutation`); the spec's
 // five-state `RunStatus` stays on the `Run` the hooks hand back. One rule, two layers.
-import { createContext, createElement, useCallback, useContext, useEffect, useMemo, useRef, useState, useSyncExternalStore } from "react";
+import { createContext, createElement, useCallback, useContext, useEffect, useLayoutEffect, useMemo, useRef, useState, useSyncExternalStore } from "react";
 import { replaceEqualDeep, shallowEqual } from "@synapse-sdk/client";
 import { toSynapseError } from "@synapse-sdk/core";
 const SynapseContext = createContext(null);
+/** `useLayoutEffect` in the browser, `useEffect` on the server (where React 18 warns on a layout effect). */
+const useLayoutEffectSafe = typeof window === "undefined" ? useEffect : useLayoutEffect;
 /**
  * Makes `node` the node of every hook below. With `useAuth` (Clerk's own `useAuth`, or `fakeAuth(token)`), the person
  * signed in there is the node's (`node.setAuth`): signed in → the node asks the key server with their credential;
  * signed out → `node.setAuth(undefined)`; not known yet → nothing; a different `userId` while signed in → a new sign-in. `useAuth` is a hook: pass it on every render or never.
- * Signing out ends no live session.
+ * Signing out ends no live session. The sign-in is set in a layout effect, so a child's effect on first mount (a
+ * `connect("<runtime>@<cluster>")`) finds it on the node.
  */
 export function SynapseProvider({ node, useAuth, children }) {
     const auth = useAuth?.();
     const getToken = useRef(auth?.getToken);
     getToken.current = auth?.getToken;
     const loaded = auth?.isLoaded, signedIn = auth?.isSignedIn, userId = auth?.userId ?? undefined;
-    useEffect(() => {
+    useLayoutEffectSafe(() => {
         if (!loaded)
             return;
         if (signedIn)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synapse-sdk/react",
-  "version": "0.3.7",
+  "version": "0.3.9",
   "description": "Synapse SDK React hooks: connection, topics, calls, services, store.",
   "type": "module",
   "sideEffects": false,
@@ -14,8 +14,8 @@
     "dist"
   ],
   "dependencies": {
-    "@synapse-sdk/core": "0.3.7",
-    "@synapse-sdk/client": "0.3.7"
+    "@synapse-sdk/core": "0.3.9",
+    "@synapse-sdk/client": "0.3.9"
   },
   "peerDependencies": {
     "react": ">=18"