You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 615ff68
Browse filesBrowse the repository at this point in the historyBrowse files
feat(examples): render a json-render dock in the minimal-next hub
Verify the JSON-render hub integration in the React/Next shell via registry
replacement (the path a non-Vue host uses, per the plan):
- The Next hub authors the shared minimal-json-render view on its hub context
and projects it onto a `json-render` dock (via @devframes/json-render/hub).
- A small in-example React registry (built on @json-render/react + the shared
@antfu/design tokens) is registered as the `json-render` renderer on the
client host; the page mounts the active dock into a panel via the renderer
registry. Next.js can't compile Vue SFCs, so the Vue @devframes/json-render-ui
isn't used here — this is registry replacement.
- UnoCSS scans the new dir + safelists the badge colors.
Docs: note the json-render dock in both hub example pages and the guide.
Created with the help of an agent.
-`mountDevframe(ctx, def)` registers any `DevframeDefinition` as a dock.
16
16
- The built-in `hub:commands:execute` RPC dispatches any registered server command, regardless of how the host was constructed.
17
17
- The browser-side `connectDevframe({ baseURL: '/__hub/' })` discovers the WS endpoint via the Next route handler at `/__hub/__connection.json`, which starts the singleton host on demand.
18
+
- The [JSON-render](/guide/json-render) hub integration with **registry replacement**: the host authors a view and projects it onto a `json-render` dock, and the React client renders it with a small in-example React registry (rather than the Vue `@devframes/json-render-ui`) — the path a non-Vue host uses.
-`mountDevframe(ctx, def)` registers any `DevframeDefinition` as a dock.
16
16
- The built-in `hub:commands:execute` RPC dispatches any registered server command, regardless of how the host was constructed.
17
17
- The browser-side `connectDevframe({ baseURL: '/__hub/' })` discovers the WS endpoint via the kit's `__connection.json` middleware.
18
+
- The opt-in [JSON-render](/guide/json-render) hub integration end to end: the host authors a view on its hub context and projects it onto a `json-render` dock, and the client host renders it via `@devframes/json-render-ui` (registered through `createDevframeClientHost({ renderers })`).
0 commit comments