refactor(devframe): remove Vite-specific coupling (#314)

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

Author: antfu

alias.ts

@@ -30,8 +30,8 @@ export const alias = {
   'devframe/adapters/kit': df('devframe/src/adapters/kit.ts'),
   'devframe/adapters/embedded': df('devframe/src/adapters/embedded.ts'),
   'devframe/adapters/mcp': df('devframe/src/adapters/mcp.ts'),
-  'devframe/helpers/nuxt/runtime/plugin.client': df('devframe/src/helpers/nuxt/runtime/plugin.client.ts'),
-  'devframe/helpers/nuxt': df('devframe/src/helpers/nuxt/index.ts'),
+  '@devframes/nuxt/runtime/plugin.client': df('nuxt/src/runtime/plugin.client.ts'),
+  '@devframes/nuxt': df('nuxt/src/index.ts'),
   'devframe/recipes/open-helpers': df('devframe/src/recipes/open-helpers.ts'),
   'devframe/client': df('devframe/src/client/index.ts'),
   'devframe': df('devframe/src'),

devframe/README.md

@@ -9,7 +9,7 @@ This directory is staged for extraction into a standalone repository. Until then
 | Path | Description |
 |------|-------------|
 | [`packages/devframe`](./packages/devframe) | The published [`devframe`](https://www.npmjs.com/package/devframe) npm package. |
-| [`docs`](./docs) | VitePress documentation site, deployed at https://devtools.vite.dev/devframe/. |
+| [`docs`](./docs) | VitePress documentation site, deployed at https://devfra.me/. |
 | [`examples`](./examples) | End-to-end demos: [`devframe-counter`](./examples/devframe-counter) (smallest cross-adapter demo) and [`devframe-files-inspector`](./examples/devframe-files-inspector) (CLI dev/build/spa + Vite DevTools dock). |
 | [`tests`](./tests) | Public-API snapshot tests via [`tsnapi`](https://github.com/posva/tsnapi). |
 
@@ -21,7 +21,7 @@ pnpm add devframe
 
 ## Documentation
 
-See [https://devtools.vite.dev/devframe/](https://devtools.vite.dev/devframe/) for the full guide and API reference.
+See [https://devfra.me/](https://devfra.me/) for the full guide and API reference.
 
 ## Adapters
 

devframe/docs/guide/devtool-definition.md

@@ -73,7 +73,7 @@ interface DevToolsNodeContext {
   readonly workspaceRoot: string
   readonly mode: 'dev' | 'build'
 
-  host: DevToolsHost // runtime abstraction (mountStatic / resolveOrigin)
+  host: DevToolsHost // runtime abstraction (mountStatic / resolveOrigin / getStorageDir)
   rpc: RpcFunctionsHost // register + broadcast + sharedState
   docks: DevToolsDockHost // dock entries
   views: DevToolsViewHost // static file hosting

devframe/docs/guide/diagnostics.md

@@ -152,7 +152,7 @@ docs/errors/
   MYP0002.md
 ```
 
-Each page covers the message, cause, example, and fix — see any [DF code page](https://devtools.vite.dev/devframe/errors/) for the canonical template. Set `docsBase` on `defineDiagnostics({...})` so the URL is auto-attached to every emitted diagnostic.
+Each page covers the message, cause, example, and fix — see any [DF code page](https://devfra.me/errors/) for the canonical template. Set `docsBase` on `defineDiagnostics({...})` so the URL is auto-attached to every emitted diagnostic.
 
 ## When to Use What
 

devframe/docs/guide/nuxt.md

@@ -4,7 +4,7 @@ outline: deep
 
 # Nuxt Helper
 
-The `devframe/helpers/nuxt` module wires a Nuxt-built SPA up as a devframe client. It's an integration helper, not a deployment adapter — it runs inside the Nuxt app that consumes your devtool, not as part of the CLI that serves it.
+The `@devframes/nuxt` module wires a Nuxt-built SPA up as a devframe client. It's an integration helper, not a deployment adapter — it runs inside the Nuxt app that consumes your devtool, not as part of the CLI that serves it.
 
 It handles the three things every Nuxt-powered standalone devtool needs to get right:
 
@@ -16,7 +16,7 @@ It handles the three things every Nuxt-powered standalone devtool needs to get r
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
-  modules: ['devframe/helpers/nuxt'],
+  modules: ['@devframes/nuxt'],
 })
 ```
 
@@ -44,7 +44,7 @@ export function usePayload() {
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
-  modules: ['devframe/helpers/nuxt'],
+  modules: ['@devframes/nuxt'],
   devframe: {
     baseURL: './', // where the devframe snapshot lives, relative to the page
     skipAppDefaults: false, // opt out of the app.baseURL / vite.base defaults
@@ -79,14 +79,14 @@ my-tool/
 ├── bin.mjs               # createCli(devtool).parse()
 ├── src/
 │   ├── cli.ts            # defineDevtool + setup(ctx) { ctx.rpc.register(...) }
-│   └── app/              # Nuxt SPA — uses `devframe/helpers/nuxt`
+│   └── app/              # Nuxt SPA — uses `@devframes/nuxt`
 └── dist/
     ├── cli.mjs           # bundled Node entry
     └── public/           # Nuxt build output, pointed at by cli.distDir
 ```
 
 - `createCli` (from `devframe/adapters/cli`) runs the Node side — HTTP + WS + static build + MCP.
-- `devframe/helpers/nuxt` handles the client side — RPC connection + base-URL plumbing.
+- `@devframes/nuxt` handles the client side — RPC connection + base-URL plumbing.
 
 They're decoupled: swap Nuxt for any other SPA framework as long as it calls `connectDevtool()` in the browser.
 

devframe/docs/guide/standalone-cli.md

@@ -90,7 +90,7 @@ For the Nuxt side, add the devframe helper module — it sets `app.baseURL: './'
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
   ssr: false,
-  modules: ['devframe/helpers/nuxt'],
+  modules: ['@devframes/nuxt'],
   nitro: {
     preset: 'static',
     output: { dir: './dist' }, // matches createCli's distDir of ./dist/public

devframe/examples/devframe-files-inspector/tests/_utils.ts

@@ -71,6 +71,7 @@ export async function startInspectorServer(
   const origin = `http://${host}:${port}`
   const h3Host = createH3DevToolsHost({
     origin,
+    appName: devtool.id,
     mount: (base, dir) =>
       app.use(base, fromNodeMiddleware(sirv(dir, { dev: true, single: true }))),
   })

devframe/examples/devframe-files-inspector/tests/kit-plugin.test.ts

@@ -14,6 +14,7 @@ describe('kit-plugin (Vite DevTools dock surface)', () => {
     const mount = vi.fn()
     const host = createH3DevToolsHost({
       origin: 'http://test.localhost',
+      appName: devtool.id,
       mount,
     })
     const ctx = await createHostContext({ cwd: process.cwd(), mode: 'dev', host })

devframe/examples/devframe-streaming-chat/tests/_utils.ts

@@ -43,6 +43,7 @@ export async function startStreamingChatServer(): Promise<StartedServer & {
   const origin = `http://${host}:${port}`
   const h3Host = createH3DevToolsHost({
     origin,
+    appName: devtool.id,
     mount: (base, dir) =>
       app.use(base, fromNodeMiddleware(sirv(dir, { dev: true, single: true }))),
   })

devframe/packages/devframe/README.md

@@ -10,7 +10,7 @@ pnpm add devframe
 
 ## Docs
 
-See the [DevFrame documentation](https://devtools.vite.dev/devframe/) for the full guide and API reference.
+See the [DevFrame documentation](https://devfra.me/) for the full guide and API reference.
 
 ## Agent-Native (experimental)
 
@@ -55,7 +55,7 @@ devframe mcp
 
 `@modelcontextprotocol/sdk` is a peer dependency — add it to your package when you want to ship MCP support.
 
-See the [Agent-Native guide](https://devtools.vite.dev/devframe/agent-native) for the full API, safety model, and Claude Desktop integration example.
+See the [Agent-Native guide](https://devfra.me/agent-native) for the full API, safety model, and Claude Desktop integration example.
 
 ## License