fix: use .js extension for ESM imports of RoutePeerKind

The imports incorrectly used .ts extension which doesn't resolve
with moduleResolution: NodeNext. Changed to .js and added 'type'
import modifier.
This commit is contained in:
quotentiroler
2026-02-08 05:35:04 -08:00
parent eb3e9c649b
commit cb24ec64f2
2 changed files with 4 additions and 2 deletions

View File

@@ -1,3 +1,4 @@
import type { RoutePeerKind } from "../routing/resolve-route.js";
import type { AgentDefaultsConfig } from "./types.agent-defaults.js";
import type { HumanDelayConfig, IdentityConfig } from "./types.base.js";
import type { GroupChatConfig } from "./types.messages.js";
@@ -74,7 +75,7 @@ export type AgentBinding = {
match: {
channel: string;
accountId?: string;
peer?: { kind: "dm" | "group" | "channel"; id: string };
peer?: { kind: RoutePeerKind; id: string };
guildId?: string;
teamId?: string;
};

View File

@@ -1,3 +1,4 @@
import type { RoutePeerKind } from "./resolve-route.js";
import { parseAgentSessionKey, type ParsedAgentSessionKey } from "../sessions/session-key-utils.js";
export {
@@ -140,7 +141,7 @@ export function buildAgentPeerSessionKey(params: {
mainKey?: string | undefined;
channel: string;
accountId?: string | null;
peerKind?: "dm" | "group" | "channel" | null;
peerKind?: RoutePeerKind | null;
peerId?: string | null;
identityLinks?: Record<string, string[]>;
/** DM session scope. */