@oddsquad/vite-plugin-lit 0.2.3 → 0.4.0

package/CHANGELOG.md

@@ -0,0 +1,112 @@
+# Changelog
+
+Notable changes per release. Versions before 0.3.0 predate this file; see the
+git history for those.
+
+## 0.4.0 — 2026-09-29
+
+A maintenance release. The timeline panel stays fast with a full buffer, the
+live inspector stops walking the whole page, and several failures that used to
+pass silently now say so. Releases are published from CI now.
+
+### Added
+
+- **Verbose render layer.** lit-html's per-part debug events (template
+  instantiation, `set part`, each binding commit) go to a new "Lit Render
+  (verbose)" layer. It is off by default, because it fires once per binding on
+  every render. Values are summarized as strings (`string:"…"`, `node:<li>`,
+  `template`, `function:onClick`) and never passed through.
+- **Releases from a version tag.** Pushing a `v*` tag runs the CI gate, checks
+  the tag against `package.json` and `CHANGELOG.md`, publishes to npm over
+  trusted publishing (OIDC), and creates the GitHub Release from the changelog
+  section. Prereleases go to the `next` dist-tag.
+
+### Changed
+
+- **The timeline list renders only the visible rows**, through
+  `@lit-labs/virtualizer`. A 2500-event recording keeps about 75 rows in the
+  DOM instead of one per event. Filtering reruns only when the events or
+  filters change.
+- **Live inspector mode no longer re-walks the page on every mutation.**
+  Batches with no custom element or shadow root in them are dropped, and
+  relevant batches walk only the subtrees they added.
+- **The docs site was rewritten** in plain language, with a tutorial, task-sized
+  DevTools guides, a troubleshooting page, screenshots in both themes, and the
+  Lit Design System's colours and type.
+
+### Fixed
+
+- The source overlay's default hotkey is Ctrl+Shift+S, as documented. The
+  runtime used to fall back to `e`, which also collided with the DevTools pick
+  command.
+- The source overlay removes its HMR listeners when it disconnects. Moving the
+  element used to register the toggle twice, so the Vite DevTools overlay
+  command did nothing, and a removed overlay kept reacting.
+- `urlSheet()` and `?css-sheet` warn when a stylesheet fails to load, and treat
+  non-ok responses as failures. A 404 used to hand Vite's fallback page to the
+  sheet as CSS, with a clean console. The sheet keeps its last good CSS.
+- An unknown `LIT_PLUGIN_HMR_ON_INCOMPATIBLE` value logs a warning and falls
+  back to the default, instead of quietly acting as `reload`.
+- The Lightning CSS pass over `css` literals finds them by parsing the module,
+  so `css`-tagged text inside a string, a comment, or another template literal
+  is no longer rewritten.
+
+## 0.3.0 — 2026-09-17
+
+The DevTools half of the plugin was rebuilt on
+[devframe](https://www.npmjs.com/package/devframe), and most of what follows
+falls out of that: the panel is no longer tied to Vite DevTools, and the same
+data it shows is reachable by a coding agent over MCP.
+
+### Added
+
+- **The panel runs on devframe.** The bespoke transport is gone. The panel
+  works docked in Vite DevTools, in its own tab, or standalone from the CLI.
+- **`lit-devtools` CLI.** `lit-devtools dev` serves the panel without a Vite
+  dev server of its own; `lit-devtools mcp` exposes the panel's data to an MCP
+  client over stdio, discovering a running dev server on its own.
+- **MCP tools for agents** — list the component tree, read recent timeline
+  events, start and stop a recording, and read why a module fell back to a full
+  reload instead of a hot patch.
+- **Updates tab.** The timeline reads as an explainer for a single update:
+  what changed, which components re-rendered, and what it cost.
+- **Session export.** A recorded session can be written out as a static copy of
+  the panel — shareable, no dev server needed to open it.
+- **Deep links.** Panel views are addressable, so a link opens the tab, the
+  selected element, or an exported snapshot at the right place.
+- **Flash on update.** An opt-in fading outline over every element that
+  finishes an update, with an optional ramp colouring it by updates per second.
+- **Ambient types for `virtual:lit-plugin/timeline`**, shipped in
+  `@oddsquad/vite-plugin-lit/client` alongside the CSS query declarations.
+  Following the custom-layers guide no longer means silencing `TS2307`.
+- **Documentation site** at <https://oddcelot.github.io/vite-plugin-lit/>, and
+  a CI workflow that type checks, lints, tests and builds every push.
+
+### Changed
+
+- Panel settings persist per developer through devframe's settings store
+  instead of per browser, so they follow you across browsers and survive
+  clearing site data. `localStorage` stays as the page's boot-time cache.
+- Source links open through the shared open-in-editor service and resolve
+  against the Vite root.
+- The docked panel draws its hover outline over a direct page channel rather
+  than routing through the dev server.
+- Tooling moved to Vite+ (oxfmt, oxlint, tsgolint); dependencies updated to
+  TypeScript 7, Vite 8.3, es-module-lexer 3 and magic-string 1.
+- The README is a front door now; the long-form guides live on the docs site.
+
+### Fixed
+
+- **`virtual:lit-plugin/timeline` broke `vite build`.** Both hooks lived on the
+  serve-only plugin, so nothing claimed the specifier during a build and the
+  bundler failed on a module the developer never wrote. It now resolves in dev
+  and build alike, stubbing itself out in any build.
+- The dev-server endpoints reject cross-site requests.
+- Source metadata is injected in the component class's own scope, so it can no
+  longer reference a class that isn't in scope.
+- The DevTools element watch survives a hot patch; `updated()` is resolved
+  lazily rather than captured once.
+- Recording state is synced to a page runtime when it connects, so a reload
+  mid-recording keeps recording.
+- `recent-events` works when called with no arguments, and the documented MCP
+  endpoint path matches the one the server serves.

package/LICENSE

@@ -0,0 +1,28 @@
+BSD 3-Clause License
+
+Copyright (c) 2017 Google LLC. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

package/README.md

@@ -0,0 +1,157 @@
+# @oddsquad/vite-plugin-lit
+
+A Vite plugin for Lit projects with true HMR, CSS delivery helpers for shadow
+roots, and a DevTools timeline.
+
+**[Documentation →](https://oddcelot.github.io/vite-plugin-lit/)**
+
+Based on `@lit-labs/vite-plugin-lit` (formerly `@lit-labs/vite-hmr`) from the
+[lit monorepo](https://github.com/lit/lit), which is kept checked out as a
+read-only [submodule](./lit) here for reference and opt-in canary testing
+against lit `main`.
+
+## Why
+
+lit-html decides "is this the same template?" by **object identity** of the
+`TemplateStringsArray`, not by content. Vite HMR re-executes an edited module,
+so a one-character edit rebuilds the component's entire subtree and takes
+focus, scroll, input state, and child `@state` with it.
+
+This plugin fixes that with two cooperating mechanisms:
+
+1. **Template-strings interning** — the `html`/`svg`/`mathml`/`css` tags are
+   wrapped in dev so strings arrays are canonicalized by content, and only the
+   edited template rebuilds its part of the DOM.
+2. **In-place class patching** — the duplicate `customElements.define` from the
+   re-executed module patches the originally-registered class in place, then
+   restores reactive property values through the new accessors.
+
+[How it works →](https://oddcelot.github.io/vite-plugin-lit/concepts/how-hmr-works/)
+
+## Usage
+
+```ts
+// vite.config.ts
+import {defineConfig} from 'vite';
+import {litPlugin} from '@oddsquad/vite-plugin-lit';
+
+export default defineConfig({
+  plugins: [litPlugin()],
+});
+```
+
+The HMR feature only applies to the dev server (`apply: 'serve'`); production
+builds are untouched. The CSS queries (`?hmr-url`, `?css-sheet`) and Lightning
+CSS literal processing apply in both dev and build.
+
+## Features
+
+- **[HMR that keeps state](https://oddcelot.github.io/vite-plugin-lit/guides/hmr/)**
+  — what survives an edit, and what falls back to a reload.
+- **[Stylesheets at scale](https://oddcelot.github.io/vite-plugin-lit/guides/stylesheets/)**
+  — one shared `CSSStyleSheet` for thousands of shadow roots, hot-swapped
+  without re-rendering, from a bare `?css-sheet` import.
+- **[DevTools timeline](https://oddcelot.github.io/vite-plugin-lit/guides/devtools/)**
+  — a layered event recorder and live component inspector inside Vite DevTools.
+- **[Source overlay](https://oddcelot.github.io/vite-plugin-lit/guides/source-overlay/)**
+  — click any element in the page to open its source in your editor.
+- **[Agent access](#coding-agents-mcp)** — the same component tree and timeline
+  as MCP tools, for coding agents.
+- **[Ecosystem support](https://oddcelot.github.io/vite-plugin-lit/guides/ecosystem/)**
+  — signals, context, tasks, and the virtualizer across a patch.
+
+Reference:
+[options](https://oddcelot.github.io/vite-plugin-lit/reference/options/) ·
+[environment variables](https://oddcelot.github.io/vite-plugin-lit/reference/environment-variables/) ·
+[import queries](https://oddcelot.github.io/vite-plugin-lit/reference/import-queries/) ·
+[runtime API](https://oddcelot.github.io/vite-plugin-lit/reference/runtime-api/) ·
+[CLI](https://oddcelot.github.io/vite-plugin-lit/reference/cli/) ·
+[limitations](https://oddcelot.github.io/vite-plugin-lit/reference/limitations/) ·
+[compatibility](https://oddcelot.github.io/vite-plugin-lit/reference/compatibility/) ·
+[benchmarks](https://oddcelot.github.io/vite-plugin-lit/reference/benchmarks/) ·
+[troubleshooting](https://oddcelot.github.io/vite-plugin-lit/guides/troubleshooting/)
+
+## Coding agents (MCP)
+
+The DevTools panel's data is also exposed as MCP tools — `lit_list-components`,
+`lit_component-details`, `lit_update-summary`, `lit_recent-events`,
+`lit_get-meta`, `lit_hmr-incompatibilities`, `lit_set-recording` — so an agent
+can read the live component tree and timeline instead of guessing from source.
+
+These answer only while a Vite dev server with DevTools is **running**. There
+is no stored data and nothing to go stale: with the server down an agent gets
+a connection error, not an empty answer.
+
+Point an MCP client at it either way:
+
+```sh
+# Auto-discovers every running dev server on this machine.
+claude mcp add lit-devtools -- npx -y @oddsquad/vite-plugin-lit mcp
+
+# Or dial one server directly, if you'd rather pin the port.
+claude mcp add lit-devtools -- npx -y mcp-remote http://localhost:5179/__devtools/__mcp
+```
+
+The equivalent `claude_desktop_config.json` / `mcp.json` entry:
+
+```json
+{
+  "mcpServers": {
+    "lit-devtools": {
+      "command": "npx",
+      "args": ["-y", "@oddsquad/vite-plugin-lit", "mcp"]
+    }
+  }
+}
+```
+
+The two differ in how the server is found, not in what it can do:
+
+- **`... vite-plugin-lit mcp`** runs devframe's connector over stdio. The
+  plugin publishes each running dev server to devframe's instance registry,
+  and the connector lists them through two gateway tools
+  (`devframe_connect_list-instances`, `devframe_connect_call-tool`) — so one
+  entry covers every project you have running, with no port to keep in sync.
+  Being a shared connector, it surfaces every devframe on the machine, not
+  only this plugin's tools.
+- **`mcp-remote <url>`** bridges stdio to one fixed URL and depends on no
+  discovery at all. Reach for it if registry discovery is unavailable — the
+  plugin logs a warning saying so at startup, naming the reason.
+
+The CLI also has `lit-devtools dev`, a standalone devframe server with no page
+attached. It exists to prove the panel definition runs without Vite (a
+framework-neutrality harness, and the groundwork for non-Vite adapters); it
+cannot show a real component tree, so it is not a way to inspect an app
+without a dev server.
+
+## Playground
+
+A manually inspectable fixture app (also the source for the e2e fixtures), and
+self-contained enough to open on
+[StackBlitz](https://stackblitz.com/github/oddcelot/vite-plugin-lit/tree/main/playground)
+straight from the repo URL. Run it locally from the repo root:
+
+```sh
+pnpm dev   # builds the plugin, then serves http://localhost:5179
+```
+
+## Development
+
+Requires Node 26 and pnpm 12 (`corepack enable` picks up the pinned version).
+The published package itself runs on Node 20 or newer.
+
+```sh
+pnpm install         # workspace: root package + playground + docs
+pnpm build           # tsc + panel assets -> ./lib, ./panel, ./index.js
+pnpm exec vp check   # format, lint, type check
+pnpm test            # unit + e2e
+pnpm docs:dev        # the documentation site
+```
+
+More in
+[Development](https://oddcelot.github.io/vite-plugin-lit/contributing/development/)
+and [Testing](https://oddcelot.github.io/vite-plugin-lit/contributing/testing/).
+
+## License
+
+BSD-3-Clause. See [LICENSE](./LICENSE).

package/bin.mjs

@@ -0,0 +1,154 @@
+#!/usr/bin/env node
+/**
+ * @license
+ * Copyright 2026 Google LLC
+ * SPDX-License-Identifier: BSD-3-Clause
+ */
+
+/**
+ * `lit-devtools` — the package's command line.
+ *
+ * Built on a bare `cac()` instance rather than devframe's `createCac()`
+ * adapter, deliberately. Two things make the wrapper the wrong fit here:
+ *
+ * 1. Its `mcp` subcommand runs `createMcpServer(definition, ...)`, which
+ *    executes the definition's `setup()` fresh and in-process. This
+ *    package's definition reads a `TimelineSource`, and a CLI has no page
+ *    to attach — so that server would answer every component query with an
+ *    empty list, forever, while looking perfectly healthy. An MCP server
+ *    that is confidently wrong is worse than no MCP server. The `mcp`
+ *    command below proxies an *already-running* dev server instead.
+ * 2. It registers `dev` as cac's default command (`[...args]`), not a named
+ *    one, and cac resolves commands first-match-wins — so its built-in
+ *    subcommands cannot be cleanly overridden after the fact, only spliced
+ *    out of `cli.commands`. Hand-rolling is less code than fighting that.
+ *
+ * `cac` and `@devframes/agentic` are optional peers, imported dynamically
+ * and only on the path that needs them, so installing this package without
+ * them stays supported.
+ *
+ * @see plans/roadmap/03-cli-and-stdio-mcp.md
+ */
+
+import process from 'node:process';
+import {createLitDevframe} from './lib/devframe/definition.js';
+import {createNullSource} from './lib/devframe/source.js';
+import {PACKAGE_VERSION} from './lib/devframe/paths.js';
+
+/**
+ * Standalone `dev` default port. Deliberately *not* the playground's 5179
+ * (`playground/vite.config.ts`): running `pnpm run dev` and `lit-devtools
+ * dev` against the same checkout is a normal thing to do while working on
+ * this package, and two servers fighting over one port is a worse first
+ * experience than a port nobody has to think about.
+ */
+const DEFAULT_DEV_PORT = 5180;
+
+/** Fail with a readable message instead of a module-resolution stack trace. */
+const requirePeer = async (specifier, hint) => {
+  try {
+    return await import(specifier);
+  } catch {
+    console.error(
+      `[lit-devtools] this command needs the optional peer "${hint}". ` +
+        `Install it and retry:\n\n  npm install -D ${hint}\n`
+    );
+    process.exit(1);
+  }
+};
+
+const main = async () => {
+  const {default: cac} = await requirePeer('cac', 'cac');
+  const cli = cac('lit-devtools');
+
+  cli
+    .command('dev', 'Start a standalone devframe dev server (no page attached)')
+    .option('--port <port>', 'Port to listen on', {default: DEFAULT_DEV_PORT})
+    .option('--host <host>', 'Host to bind to', {default: 'localhost'})
+    .option('--open', 'Open the browser on start')
+    .action(async (flags) => {
+      const {createDevServer} = await import('devframe/adapters/dev');
+      // A standalone server has no Vite and no page, so the component tree
+      // is empty by construction. This command is a framework-neutrality
+      // harness for the definition, not a way to inspect a real app --
+      // for that, run your Vite dev server with DevTools enabled.
+      await createDevServer(
+        createLitDevframe({
+          source: createNullSource(),
+          version: PACKAGE_VERSION,
+        }),
+        {
+          host: flags.host,
+          port: Number(flags.port),
+          flags: {open: Boolean(flags.open)},
+        }
+      );
+    });
+
+  cli
+    .command('build', 'Explain how to export a static snapshot of a session')
+    .action(() => {
+      // Deliberately not implemented here. A snapshot worth attaching to an
+      // issue is a *recorded session*, and the session lives in the running
+      // dev server's memory -- a fresh CLI process has no page, no timeline
+      // and no component tree, so anything it could build would be an empty
+      // shell. The export therefore runs inside the dev server that holds
+      // the data; see plans/roadmap/08-static-snapshot.md.
+      console.error(
+        `[lit-devtools] A static snapshot is exported from a running ` +
+          `session, not from this CLI.\n` +
+          `Record what you want to report in the DevTools Lit panel, then ` +
+          `press "Export snapshot" in the Timeline tab. The dev server ` +
+          `writes a self-contained panel directory you can zip onto an issue.`
+      );
+      process.exit(1);
+    });
+
+  cli
+    .command('mcp', 'Start a stdio MCP server proxying running dev servers')
+    .option(
+      '--port <port>',
+      'Also probe this port for an instance the registry does not list. ' +
+        'Probes <origin>/__connection.json at the ROOT path only, so this ' +
+        'finds a standalone "lit-devtools dev" server but NOT a ' +
+        'Vite-hosted one (mounted under /__devtools/) -- for those, rely ' +
+        'on registry discovery. Repeatable.'
+    )
+    .option(
+      '--token <token>',
+      'Bearer token presented to each instance MCP route, for a dev server ' +
+        'whose DevTools auth gate is enabled.'
+    )
+    .action(async (flags) => {
+      const {startConnectServer} = await requirePeer(
+        '@devframes/agentic/connect',
+        '@devframes/agentic'
+      );
+      // This is devframe's own generic connector: it discovers every
+      // devframe instance on the machine, not just this package's. Its two
+      // gateway tools (`devframe_connect_list-instances` /
+      // `devframe_connect_call-tool`) are how an agent reaches the `lit_*`
+      // tools, one hop in.
+      const ports = [flags.port]
+        .flat()
+        .filter((p) => p != null)
+        .map(Number)
+        .filter((p) => Number.isInteger(p) && p > 0);
+
+      await startConnectServer({
+        ...(ports.length > 0 ? {ports} : {}),
+        ...(flags.token ? {authToken: String(flags.token)} : {}),
+      });
+    });
+
+  cli.help();
+  cli.version(PACKAGE_VERSION);
+
+  cli.parse(process.argv, {run: false});
+  await cli.runMatchedCommand();
+};
+
+main().catch((error) => {
+  console.error(`[lit-devtools] ${error?.stack ?? error}`);
+  process.exit(1);
+});

package/client.d.ts

@@ -0,0 +1,61 @@
+/**
+ * @license
+ * Copyright 2026 Google LLC
+ * SPDX-License-Identifier: BSD-3-Clause
+ */
+
+/**
+ * Ambient types for the import queries provided by the Lit Vite plugin.
+ *
+ * Reference via tsconfig (`"types": ["@oddsquad/vite-plugin-lit/client"]`) or
+ * `/// <reference types="@oddsquad/vite-plugin-lit/client" />`.
+ */
+
+declare module '*.css?hmr-url' {
+  const href: string;
+  export default href;
+}
+
+declare module '*.css?css-sheet' {
+  const sheet: CSSStyleSheet;
+  export default sheet;
+}
+
+declare module 'virtual:lit-plugin/timeline' {
+  export interface TimelineLayer {
+    id: string;
+    label: string;
+    /** 0xRRGGBB */
+    color: number;
+  }
+
+  export interface TimelineEvent<TData = unknown> {
+    layerId: string;
+    /** Milliseconds since the current recording started. */
+    time: number;
+    data: TData;
+    title?: string;
+    subtitle?: string;
+    /** Pairs a start event with its matching end event in the same update group. */
+    groupId?: number | string;
+    logType?: 'default' | 'warning' | 'error';
+    /** Set by the plugin's built-in capture layers; not needed for custom events. */
+    meta?: {
+      elementId?: number;
+      tagName?: string;
+      source?: {file: string; line: number};
+    };
+  }
+
+  /**
+   * Emit a custom timeline event from app code. No-ops in production or
+   * when the `timeline` option is disabled.
+   */
+  export function addTimelineEvent(event: TimelineEvent): void;
+
+  /**
+   * Register a custom timeline layer and announce it to the panel.
+   * Idempotent — duplicate ids are ignored.
+   */
+  export function addTimelineLayer(layer: TimelineLayer): void;
+}

package/dist/client/assets/browser-agent-rpc-BXhoSh1z-CdtPhBL-.js

@@ -0,0 +1,69 @@
+import { n as onBrowserAgentToolsChanged, r as nanoid, t as listBrowserAgentTools } from "./index-DVe6M4HV.js";
+//#region node_modules/.pnpm/devframe@1.0.0_@devframes+agentic@1.0.0_cac@7.0.0_srvx@1.0.5/node_modules/devframe/dist/browser-agent-rpc-BXhoSh1z.mjs
+var CLIENT_ID_STORAGE_KEY = "devframe:client-id";
+var memoryClientId;
+/**
+* This browser tab's stable client id: one nanoid per tab, persisted in
+* `sessionStorage` so it survives page reloads and RPC reconnects. The node
+* side uses it to tell connected tabs apart across reconnects (see #394).
+*
+* Tab duplication copies `sessionStorage`, so two tabs can briefly share an id
+* until per-tab disambiguation lands with the wider tab-metadata work.
+*/
+function resolveClientId(win = globalThis.window) {
+	try {
+		const storage = win?.sessionStorage;
+		if (storage) {
+			let id = storage.getItem(CLIENT_ID_STORAGE_KEY);
+			if (!id) {
+				id = nanoid();
+				storage.setItem(CLIENT_ID_STORAGE_KEY, id);
+			}
+			return id;
+		}
+	} catch {}
+	memoryClientId ??= nanoid();
+	return memoryClientId;
+}
+/** Mirror this document's browser-agent registry over its existing RPC connection. */
+function setupBrowserAgentRpcBridge(rpc) {
+	rpc.client.register({
+		name: "devframe:agent:invoke-client-tool",
+		type: "action",
+		jsonSerializable: true,
+		handler: async (id, args) => {
+			const tool = listBrowserAgentTools().find((tool) => tool.id === id);
+			if (!tool) throw new Error(`[devframe/agent] browser tool "${id}" not found`);
+			return await tool.invoke(args);
+		}
+	});
+	let queued = false;
+	let disposed = false;
+	let lastSyncedCount = 0;
+	const sync = () => {
+		if (queued || disposed) return;
+		queued = true;
+		queueMicrotask(async () => {
+			queued = false;
+			if (disposed) return;
+			const manifests = listBrowserAgentTools().map(({ invoke: _, ...manifest }) => manifest);
+			if (manifests.length === 0 && lastSyncedCount === 0) return;
+			lastSyncedCount = manifests.length;
+			await rpc.callOptional("devframe:agent:sync-client-tools", resolveClientId(), manifests).catch(() => {});
+		});
+	};
+	const stopTools = onBrowserAgentToolsChanged(sync);
+	const stopConnection = rpc.events.on("connection:status", (status) => {
+		if (status === "connected") sync();
+	});
+	sync();
+	return () => {
+		disposed = true;
+		stopTools();
+		stopConnection();
+	};
+}
+//#endregion
+export { setupBrowserAgentRpcBridge };
+
+//# sourceMappingURL=browser-agent-rpc-BXhoSh1z-CdtPhBL-.js.map

package/dist/client/assets/browser-agent-rpc-BXhoSh1z-CdtPhBL-.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"browser-agent-rpc-BXhoSh1z-CdtPhBL-.js","names":[],"sources":["../../../node_modules/.pnpm/devframe@1.0.0_@devframes+agentic@1.0.0_cac@7.0.0_srvx@1.0.5/node_modules/devframe/dist/browser-agent-rpc-BXhoSh1z.mjs"],"sourcesContent":["import { nanoid } from \"./utils/nanoid.mjs\";\nimport { n as onBrowserAgentToolsChanged, t as listBrowserAgentTools } from \"./browser-agent-Pu-FLk6I.mjs\";\n//#region src/client/client-id.ts\nconst CLIENT_ID_STORAGE_KEY = \"devframe:client-id\";\nlet memoryClientId;\n/**\n* This browser tab's stable client id: one nanoid per tab, persisted in\n* `sessionStorage` so it survives page reloads and RPC reconnects. The node\n* side uses it to tell connected tabs apart across reconnects (see #394).\n*\n* Tab duplication copies `sessionStorage`, so two tabs can briefly share an id\n* until per-tab disambiguation lands with the wider tab-metadata work.\n*/\nfunction resolveClientId(win = globalThis.window) {\n\ttry {\n\t\tconst storage = win?.sessionStorage;\n\t\tif (storage) {\n\t\t\tlet id = storage.getItem(CLIENT_ID_STORAGE_KEY);\n\t\t\tif (!id) {\n\t\t\t\tid = nanoid();\n\t\t\t\tstorage.setItem(CLIENT_ID_STORAGE_KEY, id);\n\t\t\t}\n\t\t\treturn id;\n\t\t}\n\t} catch {}\n\tmemoryClientId ??= nanoid();\n\treturn memoryClientId;\n}\n//#endregion\n//#region src/client/browser-agent-rpc.ts\n/** Mirror this document's browser-agent registry over its existing RPC connection. */\nfunction setupBrowserAgentRpcBridge(rpc) {\n\trpc.client.register({\n\t\tname: \"devframe:agent:invoke-client-tool\",\n\t\ttype: \"action\",\n\t\tjsonSerializable: true,\n\t\thandler: async (id, args) => {\n\t\t\tconst tool = listBrowserAgentTools().find((tool) => tool.id === id);\n\t\t\tif (!tool) throw new Error(`[devframe/agent] browser tool \"${id}\" not found`);\n\t\t\treturn await tool.invoke(args);\n\t\t}\n\t});\n\tlet queued = false;\n\tlet disposed = false;\n\tlet lastSyncedCount = 0;\n\tconst sync = () => {\n\t\tif (queued || disposed) return;\n\t\tqueued = true;\n\t\tqueueMicrotask(async () => {\n\t\t\tqueued = false;\n\t\t\tif (disposed) return;\n\t\t\tconst manifests = listBrowserAgentTools().map(({ invoke: _, ...manifest }) => manifest);\n\t\t\tif (manifests.length === 0 && lastSyncedCount === 0) return;\n\t\t\tlastSyncedCount = manifests.length;\n\t\t\tawait rpc.callOptional(\"devframe:agent:sync-client-tools\", resolveClientId(), manifests).catch(() => {});\n\t\t});\n\t};\n\tconst stopTools = onBrowserAgentToolsChanged(sync);\n\tconst stopConnection = rpc.events.on(\"connection:status\", (status) => {\n\t\tif (status === \"connected\") sync();\n\t});\n\tsync();\n\treturn () => {\n\t\tdisposed = true;\n\t\tstopTools();\n\t\tstopConnection();\n\t};\n}\n//#endregion\nexport { setupBrowserAgentRpcBridge };\n"],"x_google_ignoreList":[0],"mappings":";;AAGA,IAAM,wBAAwB;AAC9B,IAAI;;;;;;;;;AASJ,SAAS,gBAAgB,MAAM,WAAW,QAAQ;CACjD,IAAI;EACH,MAAM,UAAU,KAAK;EACrB,IAAI,SAAS;GACZ,IAAI,KAAK,QAAQ,QAAQ,qBAAqB;GAC9C,IAAI,CAAC,IAAI;IACR,KAAK,OAAO;IACZ,QAAQ,QAAQ,uBAAuB,EAAE;GAC1C;GACA,OAAO;EACR;CACD,QAAQ,CAAC;CACT,mBAAmB,OAAO;CAC1B,OAAO;AACR;;AAIA,SAAS,2BAA2B,KAAK;CACxC,IAAI,OAAO,SAAS;EACnB,MAAM;EACN,MAAM;EACN,kBAAkB;EAClB,SAAS,OAAO,IAAI,SAAS;GAC5B,MAAM,OAAO,sBAAsB,CAAC,CAAC,MAAM,SAAS,KAAK,OAAO,EAAE;GAClE,IAAI,CAAC,MAAM,MAAM,IAAI,MAAM,kCAAkC,GAAG,YAAY;GAC5E,OAAO,MAAM,KAAK,OAAO,IAAI;EAC9B;CACD,CAAC;CACD,IAAI,SAAS;CACb,IAAI,WAAW;CACf,IAAI,kBAAkB;CACtB,MAAM,aAAa;EAClB,IAAI,UAAU,UAAU;EACxB,SAAS;EACT,eAAe,YAAY;GAC1B,SAAS;GACT,IAAI,UAAU;GACd,MAAM,YAAY,sBAAsB,CAAC,CAAC,KAAK,EAAE,QAAQ,GAAG,GAAG,eAAe,QAAQ;GACtF,IAAI,UAAU,WAAW,KAAK,oBAAoB,GAAG;GACrD,kBAAkB,UAAU;GAC5B,MAAM,IAAI,aAAa,oCAAoC,gBAAgB,GAAG,SAAS,CAAC,CAAC,YAAY,CAAC,CAAC;EACxG,CAAC;CACF;CACA,MAAM,YAAY,2BAA2B,IAAI;CACjD,MAAM,iBAAiB,IAAI,OAAO,GAAG,sBAAsB,WAAW;EACrE,IAAI,WAAW,aAAa,KAAK;CAClC,CAAC;CACD,KAAK;CACL,aAAa;EACZ,WAAW;EACX,UAAU;EACV,eAAe;CAChB;AACD"}