@copilotkit/web-inspector 1.66.4 → 1.67.1

package/tsdown.config.ts

@@ -1,45 +0,0 @@
-import { defineConfig } from "tsdown";
-
-export default defineConfig([
-  {
-    entry: ["src/index.ts"],
-    format: ["esm", "cjs"],
-    dts: true,
-    sourcemap: true,
-    target: "es2022",
-    outDir: "dist",
-    unbundle: true,
-    loader: {
-      ".css": "text",
-      ".svg": "dataurl",
-    },
-    exports: true,
-  },
-  {
-    entry: ["src/index.ts"],
-    format: ["umd"],
-    globalName: "CopilotKitWebInspector",
-    sourcemap: true,
-    target: "es2018",
-    outDir: "dist",
-    external: ["lit", "lit/decorators.js"],
-    loader: {
-      ".css": "text",
-      ".svg": "dataurl",
-    },
-    codeSplitting: false,
-    outputOptions(options) {
-      options.entryFileNames = "[name].umd.js";
-      options.globals = {
-        lit: "Lit",
-        "lit/decorators.js": "LitDecorators",
-        "lit/directives/style-map.js": "LitDirectivesStyleMap",
-        "lit/directives/unsafe-html.js": "LitDirectivesUnsafeHtml",
-        marked: "marked",
-        lucide: "lucide",
-        "@copilotkit/core": "CopilotKitCore",
-      };
-      return options;
-    },
-  },
-]);

package/vitest.config.ts

@@ -1,66 +0,0 @@
-import { defineConfig } from "vitest/config";
-
-// Node 25.0 unflagged the experimental Web Storage API (nodejs/node#57658),
-// so on Node 25+ a stub `window.localStorage` is installed BEFORE vitest's
-// jsdom environment runs. vitest's jsdom env does NOT replace it, so the
-// stub stays in place — and it has no `.clear()` / `.getItem()` /
-// `.setItem()` methods. Any test that touches localStorage crashes with
-// `TypeError: window.localStorage.clear is not a function`.
-//
-// This is NOT fixed by upgrading vitest or jsdom:
-//   - vitest 4.x + jsdom 29 still leave Node's stub in place — confirmed
-//     in vitest-dev/vitest#8757 (closed as "non-LTS, won't fix").
-//   - Node 25.2.0 tried throwing on access; 25.2.1 reverted it as too
-//     breaking. The real Node-side fix is targeted for Node 26.0
-//     (semver-major), no backport — see nodejs/node#60303.
-//
-// On Node 22.4–24.x, the API exists but stays behind
-// `--experimental-webstorage`, so nothing gets installed and tests pass
-// without any workaround. The bug ONLY bites on Node 25+.
-//
-// Workaround: pass `--no-experimental-webstorage` to the vitest worker so
-// Node doesn't install the stub and jsdom owns the localStorage globals
-// cleanly. This is the canonical community workaround (also used by
-// happy-dom#1950, ArkType, and the vitest#8757 thread).
-//
-// Version gate:
-//   - Lower bound (Node 22.4+): the flag only exists from Node 22.4
-//     onward. Passing it to older Node (e.g. CI's Node 20) makes Node
-//     refuse to start with "not allowed in NODE_OPTIONS". On Node
-//     22.4–24.x the flag is a harmless no-op since webstorage is still
-//     gated by --experimental-webstorage, but we keep the lower bound
-//     strict so we don't silently fail closed on Node 20.
-//   - Upper bound (Node < 26): Node 26 is expected to land the upstream
-//     fix and may remove / rename this flag as part of the unflagging
-//     cleanup. We gate the upper bound so this config doesn't blow up
-//     on Node 26+ in the future. Node 26 isn't out as of this commit,
-//     so the upper bound is purely defensive.
-//
-// When the minimum supported Node version is >=26 (which will be a long
-// time — Node 26 will likely arrive in late 2026 and need to age into
-// LTS), this whole block can be removed outright.
-const [nodeMajor, nodeMinor] = process.versions.node.split(".").map(Number);
-const needsNoExperimentalWebstorage =
-  // lower bound: flag exists (Node 22.4+)
-  (nodeMajor! > 22 || (nodeMajor === 22 && nodeMinor! >= 4)) &&
-  // upper bound: Node hasn't fixed the underlying bug yet (< 26)
-  nodeMajor! < 26;
-
-const workerExecArgv = needsNoExperimentalWebstorage
-  ? ["--no-experimental-webstorage"]
-  : [];
-
-export default defineConfig({
-  test: {
-    environment: "jsdom",
-    globals: true,
-    clearMocks: true,
-    setupFiles: ["./vitest.setup.ts"],
-    reporters: [["default", { summary: false }]],
-    silent: true,
-    poolOptions: {
-      forks: { execArgv: workerExecArgv },
-      threads: { execArgv: workerExecArgv },
-    },
-  },
-});

package/vitest.setup.ts

@@ -1,84 +0,0 @@
-// Node 25 ships an experimental built-in `localStorage` global (gated on the
-// `--localstorage-file` flag, but the accessor exists unconditionally). When
-// vitest boots the jsdom environment, jsdom defines its own `localStorage` on
-// the synthetic `window`, but Node's global accessor still wins on
-// `globalThis.localStorage` AND — because vitest's jsdom integration aliases
-// `window` to `globalThis` — also on `window.localStorage`. The result is that
-// `window.localStorage` resolves to Node's stub object which has no `clear`,
-// `setItem`, `removeItem`, etc., breaking every test that touches localStorage.
-//
-// This setup file installs a proper in-memory Storage implementation on both
-// `globalThis` and `window` BEFORE any test code runs. The shim is a plain
-// object (not a class) so `vi.spyOn(window.localStorage, "getItem")` works —
-// vitest needs the methods to be own properties on the spied target.
-//
-// We re-install the shim in `beforeEach` so a test that did
-// `vi.restoreAllMocks()` (which restores spied methods) still sees the shim's
-// methods, and so each test starts with a fresh empty store.
-
-import { beforeEach } from "vitest";
-
-import { createTelemetryEgressGuard } from "./src/lib/testing/telemetry-egress-guard.js";
-
-// No test may POST a real `oss.inspector.*` event to the live telemetry sink —
-// see the helper for why no environment variable can cover this.
-if (typeof globalThis.fetch === "function") {
-  globalThis.fetch = createTelemetryEgressGuard(globalThis.fetch);
-}
-
-function createStorageShim(): Storage {
-  const store = new Map<string, string>();
-  const shim = {
-    get length() {
-      return store.size;
-    },
-    key(index: number): string | null {
-      return Array.from(store.keys())[index] ?? null;
-    },
-    getItem(key: string): string | null {
-      return store.has(key) ? store.get(key)! : null;
-    },
-    setItem(key: string, value: string): void {
-      store.set(String(key), String(value));
-    },
-    removeItem(key: string): void {
-      store.delete(key);
-    },
-    clear(): void {
-      store.clear();
-    },
-  } as Storage;
-  return shim;
-}
-
-function installLocalStorageShim(): void {
-  const shim = createStorageShim();
-  // Override the Node 25 global accessor (and any jsdom accessor) with a
-  // plain data property pointing at our shim. `configurable: true` so a
-  // subsequent install can replace it.
-  Object.defineProperty(globalThis, "localStorage", {
-    value: shim,
-    writable: true,
-    configurable: true,
-    enumerable: true,
-  });
-  if (typeof window !== "undefined" && window !== (globalThis as unknown)) {
-    Object.defineProperty(window, "localStorage", {
-      value: shim,
-      writable: true,
-      configurable: true,
-      enumerable: true,
-    });
-  }
-}
-
-// Install once at module load so any top-level code in test files (e.g.
-// imports that read localStorage on init) sees the shim.
-installLocalStorageShim();
-
-// Re-install before each test so `vi.restoreAllMocks()` from a prior test
-// can't leave behind spied/replaced methods, and each test starts with an
-// empty store.
-beforeEach(() => {
-  installLocalStorageShim();
-});