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
feat!: remove per-plugin vite wrappers; export hub base constants from @devframes/hub/constants
Deletes three drift-prone hand-copy clusters:
- plugins/{a11y,assets,data-inspector,inspect,messages,og}/src/vite.ts
— each an 8-25 line rename over devframeVite(def, options) from
@devframes/vite/dev-spa, and the sole reason those plugins depended
on @devframes/vite. Consumers now call devframeVite() directly
against the plugin's default export; @devframes/vite moves to
devDependencies where it's still needed for the plugin's own SPA
dev config. plugin-code-server's codeServerVite and
plugin-terminals's terminalsVite are unaffected — they compose a
bridge + static plugin and build their devframe from options, which
is real behaviour beyond delegation, not a mirror.
- DEVFRAMES_HUB_BASE hand-copied across packages/{vite,nuxt,next}'s
hub-client wrappers (each commented "mirrors @devframes/hub's").
Now defined once in the client-safe packages/hub/src/constants.ts
and imported everywhere; packages/hub/src/node/initiate.ts
re-exports it for existing importers of that entry.
- normalizeBase reimplemented ×4 with two different mechanisms (ufo
vs hand-rolled). One canonical normalizeHubBase (ufo-based, hub
already depends on ufo) now lives next to the constant and is used
by @devframes/hub itself and all three framework adapters.
Also deletes packages/hub-ui/src/client/state/renderers.ts, a
30-line shim that only delegated to createDockRenderersContext; its
one call site now calls that directly.
Breaking: the six plugins' /vite export subpath is gone. Migration
documented in docs/guide/migration-0.9.md.
Created with the help of an agent.
| mount a hub inside a tool |`@devframes/{vite,nuxt,next}/hub` (+ `/hub/client`) |
45
45
46
+
**Built-in plugins**
47
+
48
+
| Removed / moved | Replacement |
49
+
|---|---|
50
+
|`@devframes/plugin-{a11y,assets,data-inspector,inspect,messages,og}/vite`|`devframeVite(def, options)` from `@devframes/vite/dev-spa`, against the plugin's default export |
51
+
46
52
## `devframe/adapters/cli` is removed
47
53
48
54
The CLI adapter was renamed to `cac` in 0.7. The `devframe/adapters/cli` entry - `createCli`, `CreateCliOptions`, and `CliHandle` - is now gone. Import from `devframe/adapters/cac` instead:
`@devframes/vite` (and `@devframes/nuxt` / `@devframes/next`) take `@devframes/hub` and `@devframes/hub-ui` as **optional** peers — only the `/hub` scope needs them. Install `vite` as a peer as before. See [`@devframes/vite`](/frameworks/vite) for the full reference.
283
289
290
+
## Built-in plugins' `/vite` subpath is removed
291
+
292
+
`a11yVitePlugin`, `assetsVitePlugin`, `dataInspectorVitePlugin`, `inspectVitePlugin`, `messagesVitePlugin`, and `ogVitePlugin` — each plugin's `@devframes/plugin-<name>/vite` export — were one-line renames over `devframeVite(def, options)`. Call `devframeVite` directly against the plugin's default export instead:
`@devframes/plugin-code-server`'s `codeServerVite` and `@devframes/plugin-terminals`'s `terminalsVite` are unaffected — they mount a bridge and a static plugin together (and build their devframe from the passed options), not a plain `devframeVite` delegation.
314
+
284
315
## `@devframes/nuxt` and `@devframes/next` split into `/dev-spa` and `/hub`
285
316
286
317
Both packages now serve their single-devframe surface from a `.../dev-spa` subpath, and the bare package root throws with a pointer to the two scopes.
0 commit comments