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
Copy file name to clipboardExpand all lines: docs/examples/index.md
-6Lines changed: 0 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,6 @@ End-to-end examples that exercise the full adapter surface, each a runnable app
14
14
|[minimal-vite-devframe-hub](./minimal-vite-devframe-hub)| Vanilla TypeScript (Vite) | A ~120-line Vite host wiring `@devframes/hub` end to end. |
15
15
|[minimal-next-devframe-hub](./minimal-next-devframe-hub)| React (Next.js) | The same hub protocol, hosted from a Next.js route handler. |
16
16
17
-
## Two kinds of example
18
-
19
-
The first three are **single-tool devframes** — one `DevframeDefinition` deployed through the [adapters](/adapters/), showing how RPC, streaming, and a chosen SPA framework fit together.
20
-
21
-
The last two are **hub hosts** built on [`@devframes/hub`](/guide/hub). They are protocol witnesses: each is a small host that exercises every hub subsystem (docks, commands, messages, terminals) so you can read one file and see the whole shape. One is a Vite plugin; the other a Next.js route handler — same hub, different host runtime.
22
-
23
17
## Run any example
24
18
25
19
Each example ships its own scripts; from the repository root:
Copy file name to clipboardExpand all lines: docs/guide/hub.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,10 @@
2
2
outline: deep
3
3
---
4
4
5
-
# Hub (multi-tool)
5
+
# Hub
6
6
7
7
`@devframes/hub` extends devframe with the orchestration features that only make sense when many devtools share a UI: a dock registry, terminal aggregation, message/toast queue, and a command palette. It does not ship UI — each framework kit (e.g. `@vitejs/devtools-kit`) provides its own UI on top of the hub's RPC + shared-state protocol.
8
8
9
-
> [!WARNING] Experimental
10
-
> The hub API surface is still being refined. Names may change before 1.0.
11
-
12
9
## What the hub adds
13
10
14
11
A hub-aware node context (`DevframeHubContext`) extends `DevframeNodeContext` with four subsystems:
Copy file name to clipboardExpand all lines: docs/guide/index.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,6 @@ outline: deep
8
8
9
9
[Vite DevTools](https://devtools.vite.dev/) is built on top of devframe. If you need an integrated multi-tool host (docks, command palette, terminals, cross-tool toasts), mount your devframe into Vite DevTools via the [`vite` adapter](/adapters/vite) — or build your own host adapter targeting any environment you like.
10
10
11
-
> [!WARNING] Experimental
12
-
> The Devframe API is still in development and may change between versions. The agent-native surface (`agent` on `defineRpcFunction`, `ctx.agent`, and the MCP adapter) is additionally flagged as experimental.
13
-
14
11
## Design principles
15
12
16
13
Devframe keeps its surface focused on one tool, so the same definition stays portable across runtimes:
0 commit comments