Frameworks
The framework kits (@devframes/vite, @devframes/nuxt, @devframes/next) integrate devframe with a meta-framework's dev server. Two subpaths:
The framework kits (@devframes/vite, @devframes/nuxt, @devframes/next) integrate devframe with a meta-framework's dev server. Two subpaths:
| Scope | Subpath | You are… |
|---|---|---|
| single | .../single | building & dev-serving a single devframe's SPA with that tool |
| hub | .../hub | mounting a whole hub (many devframes) inside that tool |
The bare package root throws, pointing to the two subpaths.
| Package | single | hub |
|---|---|---|
@devframes/vite | devframeVitePlugin / devframeViteBridge / devframeVite | viteDevframeHub (+ /hub/client) |
@devframes/nuxt | the Nuxt module (modules: ['@devframes/nuxt/single']) | the hub Nuxt module (+ /hub/client) |
@devframes/next | withDevframe + createDevframeNextHandler (+ /single/client) | nextDevframeHub (+ /hub/client) |
single: author one devframe
For framework-neutral CLI/build/embedded outputs, use the adapters instead.
hub: mount a hub
Each hub scope wraps initHub and defaults the UI to @devframes/hub-ui's createUi() (ui to override, ui: false for headless). Per tool: Vite, Nuxt, Next.
@devframes/vite/hub and @devframes/nuxt/hub recommend the native hub UI providers (Vite DevTools, Nuxt DevTools) once (silence with { quiet: true }). Next has none, so @devframes/next/hub stays quiet.