@memberjunction/ai-bridge-livekit 0.0.1 → 5.42.0

package/dist/livekit-sdk.d.ts

@@ -0,0 +1,187 @@
+/**
+ * The injectable **LiveKit room SDK seam** — the minimal set of operations
+ * {@link import('./livekit-bridge.js').LiveKitBridge} needs from LiveKit, declared as an interface so the
+ * driver builds and unit-tests against an in-memory fake with **no network and no real LiveKit SDK**.
+ *
+ * ## LiveKit is the MJ-NATIVE room (self-hosted), not a 3rd-party platform
+ * Every OTHER bridge in this program connects **out** to a meeting hosted by someone else (Zoom,
+ * Teams, Meet, Webex, Slack, Discord) or to a telephony carrier (Twilio, Vonage, RingCentral). LiveKit
+ * is the opposite: it is an **open-source WebRTC SFU that MJ runs itself** — the "MJ-native room"
+ * (`/plans/realtime/realtime-bridges-architecture.md` §4c). The architecture deliberately treats a Zoom
+ * meeting, a Teams meeting, and an MJ-native LiveKit room **identically** — all are multi-party media
+ * transports — so LiveKit is "*another bridge, not a special build*." The only practical differences:
+ * - **We own the room.** No marketplace review, no per-platform bot-admission quirks; MJ mints the
+ *   access token and the room exists because MJ stood up the SFU. An MJ-native multi-party experience
+ *   (e.g. embedded in Explorer) is just *this* bridge.
+ * - **`connect(roomUrl, token)`** takes a LiveKit room URL + a signed access token (minted upstream by
+ *   MJ's credential/token layer — never inline secrets), rather than a join URL we were handed.
+ *
+ * ## Production binding (TODO at deployment)
+ * In production this interface is bound to **`livekit-server-sdk`** (token minting / room admin) plus a
+ * **room client** (the Node WebRTC participant — e.g. `@livekit/rtc-node`) so the bot can publish/
+ * subscribe media. The named operations map to the SDK as follows:
+ * - {@link connect} / {@link disconnect} → the room client `connect()` / `disconnect()` lifecycle.
+ * - {@link publishAudioFrame} → publishing PCM on the bot's audio track (the agent's voice).
+ * - {@link onAudioTrack} → subscribing each remote participant's audio track; LiveKit delivers tracks
+ *   **per participant**, which is the native source of speaker labels for diarization (no extra mixer).
+ * - {@link publishVideoFrame} / {@link publishScreenFrame} → publishing the bot's camera / screen-share
+ *   tracks (LiveKit does full A/V/screen; the realtime models light audio first).
+ * - {@link onParticipantJoin} / {@link onParticipantLeave} / {@link getParticipants} → the room's
+ *   `ParticipantConnected` / `ParticipantDisconnected` events + the participant list.
+ * - {@link sendDataMessage} → the LiveKit **data channel** (reliable data publish) — used for chat.
+ * - {@link onDisconnected} → the room `Disconnected` event (the SFU closed / the bot was removed).
+ *
+ * ## Echo / self-audio
+ * A LiveKit SFU **never delivers a participant its own published track back** — the bot does not hear
+ * its own voice, so no echo gate is needed here (documented in {@link onAudioTrack}). The bridge still
+ * flags its own track via {@link LiveKitParticipant.IsLocal} defensively.
+ *
+ * Binding the real SDK is a thin adapter that implements this interface; the driver and its tests do
+ * not change. **None of the SDK types leak into this package.**
+ *
+ * See `/plans/realtime/realtime-bridges-architecture.md` §4c and `/guides/REALTIME_BRIDGES_GUIDE.md`.
+ */
+/** The role a LiveKit participant holds, normalized to the bridge's participant roles. */
+export type LiveKitParticipantRole = 'Host' | 'CoHost' | 'Participant';
+/**
+ * One LiveKit room participant as the seam reports it. Platform-native and minimal — the driver maps
+ * this onto `BridgeParticipantInfo` / `BridgeMeetingParticipant`.
+ */
+export interface LiveKitParticipant {
+    /** The LiveKit participant identity (stable, application-assigned — the SID's human-facing key). */
+    Identity: string;
+    /** The participant's display name as LiveKit reports it (the `name` attribute), when set. */
+    DisplayName?: string;
+    /** The participant's room role (derived from participant metadata / permissions by the adapter). */
+    Role: LiveKitParticipantRole;
+    /** Whether this participant is the bridge's own bot (LiveKit's local participant). */
+    IsLocal?: boolean;
+}
+/**
+ * One frame of raw per-participant audio the seam surfaces for diarization + the agent's "hearing".
+ * Because LiveKit subscribes tracks **per participant**, every inbound frame is already attributed to a
+ * single speaker — diarization comes free from the SFU.
+ */
+export interface LiveKitAudioFrame {
+    /** Raw PCM audio bytes for this frame. */
+    Pcm: ArrayBuffer;
+    /** The LiveKit participant identity this audio came from (the diarization speaker label). */
+    ParticipantIdentity: string;
+    /** The participant's display name at capture time, when known. */
+    DisplayName?: string;
+    /** Optional epoch-ms capture timestamp. */
+    TimestampMs?: number;
+}
+/** Arguments to {@link ILiveKitRoomSdk.connect} — what the bot needs to join an MJ-native room. */
+export interface LiveKitConnectArgs {
+    /** The LiveKit room server URL (e.g. `wss://livekit.myorg.com`). MJ-owned, self-hosted. */
+    RoomUrl: string;
+    /**
+     * The signed LiveKit access token authorizing the bot to join a specific room as a participant.
+     * Minted upstream by MJ's token/credential layer (it encodes the room name + grants). Never inline
+     * secrets — this arrives already-signed.
+     */
+    AccessToken: string;
+    /** The display name the bot appears as in the participant list. */
+    BotDisplayName: string;
+}
+/** The handles the seam returns after a successful {@link ILiveKitRoomSdk.connect}. */
+export interface LiveKitConnectResult {
+    /** The bot's own participant identity in the joined room. */
+    BotIdentity: string;
+    /** The LiveKit room name the bot joined (the durable external connection id). */
+    RoomName: string;
+}
+/**
+ * The minimal LiveKit room SDK surface the {@link import('./livekit-bridge.js').LiveKitBridge} depends on.
+ * Production binds this to `livekit-server-sdk` + a room client; tests inject a `FakeLiveKitRoomSdk`.
+ */
+export interface ILiveKitRoomSdk {
+    /**
+     * Connects to the MJ-native LiveKit room as a bot participant and brings the bot online. Returns
+     * the bot's identity + the room name.
+     *
+     * @param args Connect parameters (room URL, signed access token, bot name).
+     * @returns The bot identity + room handles.
+     */
+    connect(args: LiveKitConnectArgs): Promise<LiveKitConnectResult>;
+    /** Disconnects from the room and releases SDK resources. */
+    disconnect(): Promise<void>;
+    /**
+     * Publishes one raw PCM audio frame on the bot's audio track (the agent's voice into the room).
+     *
+     * @param pcm The PCM audio bytes to publish.
+     */
+    publishAudioFrame(pcm: ArrayBuffer): void;
+    /**
+     * Flushes all pending/queued outbound audio (the agent's voice). Called on barge-in so the agent
+     * stops talking immediately instead of draining already-buffered audio after the model is cut off.
+     */
+    flushOutboundAudio(): void;
+    /**
+     * Subscribes inbound per-participant audio frames (what the agent hears, carrying the speaker
+     * identity for diarization). "Latest handler wins." The SFU never echoes the bot's own published
+     * audio back, so frames here are always from OTHER participants.
+     *
+     * @param cb Invoked with each inbound, per-participant audio frame.
+     */
+    onAudioTrack(cb: (frame: LiveKitAudioFrame) => void): void;
+    /**
+     * Publishes one raw video frame on the bot's camera track. LiveKit does full video; the realtime
+     * models light audio first, so this is wired but typically unused until a model emits video.
+     *
+     * @param frame The encoded/raw video frame bytes to publish.
+     */
+    publishVideoFrame(frame: ArrayBuffer): void;
+    /**
+     * Publishes one raw screen-share frame on the bot's screen track (e.g. a Remote Browser channel's
+     * viewport). LiveKit does full screen share.
+     *
+     * @param frame The encoded/raw screen frame bytes to publish.
+     */
+    publishScreenFrame(frame: ArrayBuffer): void;
+    /**
+     * Registers a callback fired when a participant connects. "Latest handler wins."
+     *
+     * @param cb Invoked with the participant who joined.
+     */
+    onParticipantJoin(cb: (participant: LiveKitParticipant) => void): void;
+    /**
+     * Registers a callback fired when a participant disconnects. "Latest handler wins."
+     *
+     * @param cb Invoked with the participant identity that left.
+     */
+    onParticipantLeave(cb: (participantIdentity: string) => void): void;
+    /**
+     * Returns the current participant list (including the bot).
+     *
+     * @returns The current participants.
+     */
+    getParticipants(): Promise<LiveKitParticipant[]>;
+    /**
+     * Sends a text message on the LiveKit data channel (reliable publish to all participants) — the
+     * room-native "chat".
+     *
+     * @param text The chat/data message text.
+     */
+    sendDataMessage(text: string): Promise<void>;
+    /**
+     * Registers a callback fired when the room disconnects the bot (SFU closed / bot removed). "Latest
+     * handler wins."
+     *
+     * @param cb Invoked when the room has disconnected.
+     */
+    onDisconnected(cb: () => void): void;
+}
+/**
+ * A factory that constructs an {@link ILiveKitRoomSdk} for a session — the creation seam (mirroring
+ * Zoom's `ZoomMeetingSdkFactory`). Production supplies a factory that builds the real LiveKit adapter
+ * (`livekit-server-sdk` + a room client) from resolved config; tests supply one that returns a
+ * `FakeLiveKitRoomSdk`.
+ *
+ * @param config The resolved provider/session configuration (room URL, region, credential refs already
+ *   resolved upstream into a signed token).
+ * @returns The LiveKit room SDK instance to drive the room with.
+ */
+export type LiveKitRoomSdkFactory = (config?: Record<string, unknown>) => ILiveKitRoomSdk;
+//# sourceMappingURL=livekit-sdk.d.ts.map

package/dist/livekit-sdk.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"livekit-sdk.d.ts","sourceRoot":"","sources":["../src/livekit-sdk.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA0CG;AAEH,0FAA0F;AAC1F,MAAM,MAAM,sBAAsB,GAAG,MAAM,GAAG,QAAQ,GAAG,aAAa,CAAC;AAEvE;;;GAGG;AACH,MAAM,WAAW,kBAAkB;IAC/B,oGAAoG;IACpG,QAAQ,EAAE,MAAM,CAAC;IACjB,6FAA6F;IAC7F,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,oGAAoG;IACpG,IAAI,EAAE,sBAAsB,CAAC;IAC7B,sFAAsF;IACtF,OAAO,CAAC,EAAE,OAAO,CAAC;CACrB;AAED;;;;GAIG;AACH,MAAM,WAAW,iBAAiB;IAC9B,0CAA0C;IAC1C,GAAG,EAAE,WAAW,CAAC;IACjB,6FAA6F;IAC7F,mBAAmB,EAAE,MAAM,CAAC;IAC5B,kEAAkE;IAClE,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,2CAA2C;IAC3C,WAAW,CAAC,EAAE,MAAM,CAAC;CACxB;AAED,mGAAmG;AACnG,MAAM,WAAW,kBAAkB;IAC/B,2FAA2F;IAC3F,OAAO,EAAE,MAAM,CAAC;IAChB;;;;OAIG;IACH,WAAW,EAAE,MAAM,CAAC;IACpB,mEAAmE;IACnE,cAAc,EAAE,MAAM,CAAC;CAC1B;AAED,uFAAuF;AACvF,MAAM,WAAW,oBAAoB;IACjC,6DAA6D;IAC7D,WAAW,EAAE,MAAM,CAAC;IACpB,iFAAiF;IACjF,QAAQ,EAAE,MAAM,CAAC;CACpB;AAED;;;GAGG;AACH,MAAM,WAAW,eAAe;IAC5B;;;;;;OAMG;IACH,OAAO,CAAC,IAAI,EAAE,kBAAkB,GAAG,OAAO,CAAC,oBAAoB,CAAC,CAAC;IAEjE,4DAA4D;IAC5D,UAAU,IAAI,OAAO,CAAC,IAAI,CAAC,CAAC;IAE5B;;;;OAIG;IACH,iBAAiB,CAAC,GAAG,EAAE,WAAW,GAAG,IAAI,CAAC;IAE1C;;;OAGG;IACH,kBAAkB,IAAI,IAAI,CAAC;IAE3B;;;;;;OAMG;IACH,YAAY,CAAC,EAAE,EAAE,CAAC,KAAK,EAAE,iBAAiB,KAAK,IAAI,GAAG,IAAI,CAAC;IAE3D;;;;;OAKG;IACH,iBAAiB,CAAC,KAAK,EAAE,WAAW,GAAG,IAAI,CAAC;IAE5C;;;;;OAKG;IACH,kBAAkB,CAAC,KAAK,EAAE,WAAW,GAAG,IAAI,CAAC;IAE7C;;;;OAIG;IACH,iBAAiB,CAAC,EAAE,EAAE,CAAC,WAAW,EAAE,kBAAkB,KAAK,IAAI,GAAG,IAAI,CAAC;IAEvE;;;;OAIG;IACH,kBAAkB,CAAC,EAAE,EAAE,CAAC,mBAAmB,EAAE,MAAM,KAAK,IAAI,GAAG,IAAI,CAAC;IAEpE;;;;OAIG;IACH,eAAe,IAAI,OAAO,CAAC,kBAAkB,EAAE,CAAC,CAAC;IAEjD;;;;;OAKG;IACH,eAAe,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC;IAE7C;;;;;OAKG;IACH,cAAc,CAAC,EAAE,EAAE,MAAM,IAAI,GAAG,IAAI,CAAC;CACxC;AAED;;;;;;;;;GASG;AACH,MAAM,MAAM,qBAAqB,GAAG,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,KAAK,eAAe,CAAC"}

package/dist/livekit-sdk.js

@@ -0,0 +1,45 @@
+/**
+ * The injectable **LiveKit room SDK seam** — the minimal set of operations
+ * {@link import('./livekit-bridge.js').LiveKitBridge} needs from LiveKit, declared as an interface so the
+ * driver builds and unit-tests against an in-memory fake with **no network and no real LiveKit SDK**.
+ *
+ * ## LiveKit is the MJ-NATIVE room (self-hosted), not a 3rd-party platform
+ * Every OTHER bridge in this program connects **out** to a meeting hosted by someone else (Zoom,
+ * Teams, Meet, Webex, Slack, Discord) or to a telephony carrier (Twilio, Vonage, RingCentral). LiveKit
+ * is the opposite: it is an **open-source WebRTC SFU that MJ runs itself** — the "MJ-native room"
+ * (`/plans/realtime/realtime-bridges-architecture.md` §4c). The architecture deliberately treats a Zoom
+ * meeting, a Teams meeting, and an MJ-native LiveKit room **identically** — all are multi-party media
+ * transports — so LiveKit is "*another bridge, not a special build*." The only practical differences:
+ * - **We own the room.** No marketplace review, no per-platform bot-admission quirks; MJ mints the
+ *   access token and the room exists because MJ stood up the SFU. An MJ-native multi-party experience
+ *   (e.g. embedded in Explorer) is just *this* bridge.
+ * - **`connect(roomUrl, token)`** takes a LiveKit room URL + a signed access token (minted upstream by
+ *   MJ's credential/token layer — never inline secrets), rather than a join URL we were handed.
+ *
+ * ## Production binding (TODO at deployment)
+ * In production this interface is bound to **`livekit-server-sdk`** (token minting / room admin) plus a
+ * **room client** (the Node WebRTC participant — e.g. `@livekit/rtc-node`) so the bot can publish/
+ * subscribe media. The named operations map to the SDK as follows:
+ * - {@link connect} / {@link disconnect} → the room client `connect()` / `disconnect()` lifecycle.
+ * - {@link publishAudioFrame} → publishing PCM on the bot's audio track (the agent's voice).
+ * - {@link onAudioTrack} → subscribing each remote participant's audio track; LiveKit delivers tracks
+ *   **per participant**, which is the native source of speaker labels for diarization (no extra mixer).
+ * - {@link publishVideoFrame} / {@link publishScreenFrame} → publishing the bot's camera / screen-share
+ *   tracks (LiveKit does full A/V/screen; the realtime models light audio first).
+ * - {@link onParticipantJoin} / {@link onParticipantLeave} / {@link getParticipants} → the room's
+ *   `ParticipantConnected` / `ParticipantDisconnected` events + the participant list.
+ * - {@link sendDataMessage} → the LiveKit **data channel** (reliable data publish) — used for chat.
+ * - {@link onDisconnected} → the room `Disconnected` event (the SFU closed / the bot was removed).
+ *
+ * ## Echo / self-audio
+ * A LiveKit SFU **never delivers a participant its own published track back** — the bot does not hear
+ * its own voice, so no echo gate is needed here (documented in {@link onAudioTrack}). The bridge still
+ * flags its own track via {@link LiveKitParticipant.IsLocal} defensively.
+ *
+ * Binding the real SDK is a thin adapter that implements this interface; the driver and its tests do
+ * not change. **None of the SDK types leak into this package.**
+ *
+ * See `/plans/realtime/realtime-bridges-architecture.md` §4c and `/guides/REALTIME_BRIDGES_GUIDE.md`.
+ */
+export {};
+//# sourceMappingURL=livekit-sdk.js.map

package/dist/livekit-sdk.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"livekit-sdk.js","sourceRoot":"","sources":["../src/livekit-sdk.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA0CG"}

package/dist/register-native.d.ts

@@ -0,0 +1,19 @@
+/**
+ * @fileoverview Registers the LiveKit **native two-way** SDK binding into the {@link BridgeNativeSdkRegistry}
+ * so `AIBridgeEngine.StartBridgeSession` auto-binds it onto a resolved `LiveKitBridge` before connect — no
+ * per-deployment wiring needed. The typed downcast + `SetSdkFactory` stay confined here (where the concrete
+ * `LiveKitBridge` type is known), keeping the engine seam free of provider types.
+ *
+ * A host can still override per-session via `StartBridgeSessionParams.BindSdk` — e.g. to inject a fake in a
+ * test instead of the native two-way default.
+ *
+ * @module @memberjunction/ai-bridge-livekit
+ * @author MemberJunction.com
+ */
+/**
+ * Registers LiveKit's native two-way binding. Idempotent (latest-wins in the registry), and invoked from the
+ * package `index.ts` so merely importing `@memberjunction/ai-bridge-livekit` wires the default binding. Also
+ * exported as a tree-shake-safe no-op-returning function callers can reference to force-retain the module.
+ */
+export declare function RegisterLiveKitNativeSdk(): void;
+//# sourceMappingURL=register-native.d.ts.map

package/dist/register-native.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"register-native.d.ts","sourceRoot":"","sources":["../src/register-native.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AASH;;;;GAIG;AACH,wBAAgB,wBAAwB,IAAI,IAAI,CAO/C"}

package/dist/register-native.js

@@ -0,0 +1,32 @@
+/**
+ * @fileoverview Registers the LiveKit **native two-way** SDK binding into the {@link BridgeNativeSdkRegistry}
+ * so `AIBridgeEngine.StartBridgeSession` auto-binds it onto a resolved `LiveKitBridge` before connect — no
+ * per-deployment wiring needed. The typed downcast + `SetSdkFactory` stay confined here (where the concrete
+ * `LiveKitBridge` type is known), keeping the engine seam free of provider types.
+ *
+ * A host can still override per-session via `StartBridgeSessionParams.BindSdk` — e.g. to inject a fake in a
+ * test instead of the native two-way default.
+ *
+ * @module @memberjunction/ai-bridge-livekit
+ * @author MemberJunction.com
+ */
+import { BridgeNativeSdkRegistry } from '@memberjunction/ai-bridge-base';
+import { BindLiveKitNative } from './livekit-native-sdk.js';
+/** The `MJ: AI Bridge Providers.DriverClass` value the LiveKit provider row carries. */
+const LIVEKIT_DRIVER_CLASS = 'LiveKitBridge';
+/**
+ * Registers LiveKit's native two-way binding. Idempotent (latest-wins in the registry), and invoked from the
+ * package `index.ts` so merely importing `@memberjunction/ai-bridge-livekit` wires the default binding. Also
+ * exported as a tree-shake-safe no-op-returning function callers can reference to force-retain the module.
+ */
+export function RegisterLiveKitNativeSdk() {
+    BridgeNativeSdkRegistry.Instance.Register(LIVEKIT_DRIVER_CLASS, (driver) => {
+        // Safe downcast: the registry is keyed by DriverClass, so the engine only ever applies this to the
+        // LiveKitBridge it resolved for 'LiveKitBridge'. BindLiveKitNative() defaults to the lazy native
+        // loader, which reads NativeModuleSpecifier from the per-session Configuration.
+        driver.SetSdkFactory(BindLiveKitNative());
+    });
+}
+// Register on import (mirrors the LoadLiveKitBridge() tree-shake pattern in index.ts).
+RegisterLiveKitNativeSdk();
+//# sourceMappingURL=register-native.js.map

package/dist/register-native.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"register-native.js","sourceRoot":"","sources":["../src/register-native.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,uBAAuB,EAAsB,MAAM,gCAAgC,CAAC;AAE7F,OAAO,EAAE,iBAAiB,EAAE,MAAM,sBAAsB,CAAC;AAEzD,wFAAwF;AACxF,MAAM,oBAAoB,GAAG,eAAe,CAAC;AAE7C;;;;GAIG;AACH,MAAM,UAAU,wBAAwB;IACpC,uBAAuB,CAAC,QAAQ,CAAC,QAAQ,CAAC,oBAAoB,EAAE,CAAC,MAA0B,EAAE,EAAE;QAC3F,mGAAmG;QACnG,iGAAiG;QACjG,gFAAgF;QAC/E,MAAwB,CAAC,aAAa,CAAC,iBAAiB,EAAE,CAAC,CAAC;IACjE,CAAC,CAAC,CAAC;AACP,CAAC;AAED,uFAAuF;AACvF,wBAAwB,EAAE,CAAC"}

package/package.json

@@ -1,10 +1,35 @@
 {
   "name": "@memberjunction/ai-bridge-livekit",
-  "version": "0.0.1",
-  "description": "OIDC trusted publishing setup package for @memberjunction/ai-bridge-livekit",
-  "keywords": [
-    "oidc",
-    "trusted-publishing",
-    "setup"
-  ]
+  "type": "module",
+  "version": "5.42.0",
+  "description": "MemberJunction: LiveKit Realtime Bridge driver — the MJ-native multi-party room. Unlike the other bridges (which connect OUT to a 3rd-party meeting platform), LiveKit is a SELF-HOSTED WebRTC SFU that MJ runs itself. Connects the realtime agent engine to a LiveKit room as a bot participant (audio/video/screen in+out, per-participant diarization, data-channel chat) via an injectable LiveKit room SDK seam, and contributes a Meeting Controls facilitator channel.",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "files": [
+    "/dist"
+  ],
+  "scripts": {
+    "start": "ts-node-dev src/index.ts",
+    "build": "tsc && tsc-alias -f",
+    "test": "vitest run",
+    "test:watch": "vitest"
+  },
+  "author": "MemberJunction.com",
+  "license": "ISC",
+  "dependencies": {
+    "@memberjunction/core": "5.42.0",
+    "@memberjunction/global": "5.42.0",
+    "@memberjunction/core-entities": "5.42.0",
+    "@memberjunction/ai-bridge-base": "5.42.0"
+  },
+  "devDependencies": {
+    "@types/node": "24.10.11",
+    "ts-node-dev": "^2.0.0",
+    "typescript": "^5.9.3",
+    "vitest": "^4.0.18"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/MemberJunction/MJ"
+  }
 }