@unitninety/site-kit 0.0.0-stage → 1.6.2

package/src/bridge/client.tsx

@@ -0,0 +1,66 @@
+'use client'
+
+import { usePathname, useRouter } from 'next/navigation'
+import { useEffect, useRef, useTransition } from 'react'
+
+import { createBridge, type Bridge } from './createBridge'
+
+/**
+ * Mounted only in draft (by `EditingProvider`, itself mounted only by `U90Bridge` when
+ * `draftMode()` is enabled). Does nothing when this page is not framed — `window.parent ===
+ * window` — so a draft page opened directly, outside the Canvas, never starts the bridge.
+ *
+ * Renders nothing; all of its work is the `createBridge` instance it starts and stops, plus the
+ * `usePathname()` effect below that reports a client-side navigation as `u90:path`.
+ */
+export function BridgeClient({ platformOrigin, onSelect }: { platformOrigin: string; onSelect?: (path: string | null) => void }) {
+  const router = useRouter()
+  const bridgeRef = useRef<Bridge | null>(null)
+  /*
+   * `router.refresh()` commits seconds after it is called. Run as a transition, `isPending` is true
+   * until the new tree commits. React-owned block moves remain live; legacy DOM-moving previews
+   * wait for that commit (`createBridge`'s `refreshing`). The bridge sets its own flag the moment it asks, so there is no
+   * gap before `isPending` is first seen.
+   */
+  const [isPending, startTransition] = useTransition()
+
+  useEffect(() => {
+    if (window.parent === window) return
+
+    const bridge = createBridge(window, {
+      platformOrigin,
+      parent: window.parent,
+      refresh: () => startTransition(() => router.refresh()),
+      onSelect,
+    })
+    bridgeRef.current = bridge
+    bridge.start()
+    return () => {
+      bridge.stop()
+      bridgeRef.current = null
+    }
+  }, [platformOrigin, router, onSelect])
+
+  // Only the end matters: the bridge marks the start itself. A slow refresh warns; only a real completion releases its boundary.
+  useEffect(() => {
+    if (!isPending) bridgeRef.current?.setRefreshing(false)
+  }, [isPending])
+
+  /*
+   * `u90:path`, for a client-side navigation (a `<Link>`, `router.push`, …) — the initial path
+   * is already carried by `ready`, sent from `start()` above, so the first run of this effect
+   * (the initial render, before any navigation has happened) is skipped rather than sending a
+   * redundant duplicate of it.
+   */
+  const pathname = usePathname()
+  const isFirstPath = useRef(true)
+  useEffect(() => {
+    if (isFirstPath.current) {
+      isFirstPath.current = false
+      return
+    }
+    bridgeRef.current?.notifyPath(pathname)
+  }, [pathname])
+
+  return null
+}