…ng (#322)

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…DMEs (#323)

…it (#327)

JSON-render is a hub-layer concern: the spec is rendered by the
Vite DevTools component catalog, the renderer handle is only
consumable via a `DevToolsViewJsonRender` dock entry (kit type),
and every example pairs `createJsonRenderer` with
`ctx.docks.register({ type: 'json-render', ui })`. Move types,
factory, and `defineJsonRenderSpec` to `@vitejs/devtools-kit` so
the API lives in the package that owns the runtime contract;
`DevToolsNodeContext` is now framework-neutral as intended.

BREAKING: `ctx.createJsonRenderer` is no longer on
`DevToolsNodeContext`; use `KitNodeContext` (passed to
`Plugin.devtools.setup` and `createPluginFromDevframe`'s
`options.setup`). All in-repo consumers already run under kit.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Renames the singular `devtool` terminology throughout the devframe
package to `devframe`, matching the package name and positioning.

Canonical names: `defineDevframe`, `DevframeDefinition`,
`DevframeRuntime`, `DevframeDeploymentKind`, `DevframeCliOptions`,
`DevframeSpaOptions`, `DevframeBrowserContext`, `DevframeSetupInfo`,
`connectDevframe`.

The old names (`defineDevtool`, `DevtoolDefinition`, `connectDevtool`,
etc.) continue to work as deprecated aliases — types carry
`@deprecated` JSDoc, and `defineDevtool` / `connectDevtool` emit a
one-time `console.warn` on first call before delegating to the new
name.

Updated source, kit bridge, Nuxt package, docs, examples, skill
templates, READMEs, and CLAUDE.md/AGENTS.md. The `Vite DevTools`
product name and `DevTools*` (PascalCase plural) identifiers stay
unchanged.

…ware })` and Nuxt module (#329)

Adds `devMiddleware` to `createVitePlugin` so a host Vite/Nuxt/Astro app
can own the SPA while devframe owns the RPC + WS backend. The plugin
starts `createDevServer` in bridge mode (no sirv mount) on a resolved
port and serves `<base>__connection.json` via Vite middleware so the
host-served SPA can discover the WS endpoint.

The `@devframes/nuxt` module gains a matching `devframe` + `devMiddleware`
pair. Passing `devframe` is the only step required — the bridge defaults
on, auto-reads `nuxt.options.devServer.host` so `nuxt dev --host`
propagates, and tears down cleanly on Vite restart / Nuxt close.

`createDevServer`'s `distDir` is now truly optional (bridge mode). New
`DF0033` (warn) covers bridge startup failures.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Add a small in-tree utility at `devframe/utils/serve-static` exposing
`serveStaticHandler` (h3 event handler) and `serveStaticNodeMiddleware`
(Connect-compatible) backed by a shared file-resolution function with
SPA fallback, MIME via `mrmime`, HEAD short-circuit, and path-traversal
guard. Swap all 8 sirv call sites across devframe adapters, kit's Vite
host, core's server + CLI, and example test utilities. Drop `sirv` from
the workspace catalog and from every package.json that listed it
(including two orphan entries in `packages/{rolldown,vite}` that never
imported it).

* refactor(devframe): bundle deps and expose them as minimal utils/*

Bundle open, launch-editor, ohash, immer, ansis, and structured-clone-es
into devframe and expose them through stable utils/* subpaths with
minimal, swap-friendly wrappers. Audit the existing utils to wrap bare
re-exports (human-id, whenexpr) and stop leaking immer's Patch/Objectish
types from shared-state. Drop the now-unused utils/state.ts duplicate.
Migrate all internal call sites to the new util paths and drop the
now-transitive deps from packages/{core,kit,vite,rolldown}.

* docs(devframe): document bundled utils/* helpers

Add a dedicated Utilities page listing every `devframe/utils/*` export
(colors, open, launch-editor, hash, structured-clone, human-id, nanoid,
promise, events, shared-state, streaming-channel, when), wired into the
sidebar and the guide landing page. Drop install-separately language
from the standalone-cli recipe (the `launch-editor` peer-dep note) and
soften the immer references in shared-state.md, since both are now
internal implementation details. Add a Bundled utilities section to the
devframe agent skill so agents know which helpers ship in-box.

…ode` (#332)

BREAKING CHANGE: auth helpers (`getTempAuthToken`, `refreshTempAuthToken`,
`consumeTempAuthToken`, `getPendingAuth`, `setPendingAuth`, `abortPendingAuth`,
`PendingAuthRequest`, `revokeAuthToken`, `revokeActiveConnectionsForToken`)
no longer re-export from `devframe/node` — import from `devframe/node/auth`.

The `devframe/internal` sub-export is renamed to `devframe/node/internal`,
which also now hosts the relocated `context-internal.ts`. End users were
never meant to depend on this subpath; first-party adapters update accordingly.