@builder.io/dev-tools 1.18.11-dev.202511202306.80563b8f8 → 1.18.11-dev.202511202319.621aec6ae

package/types/cli/utils/file-overrides-manager.d.ts

@@ -1,26 +1,26 @@
 export interface FileOverride {
-    /**
-     * Path where the file should be written.
-     * - Absolute paths: "/app/.env", "/etc/config/app.conf"
-     * - Tilde expansion: "~/.config/app.json" (expands to home directory)
-     * - Relative paths: "./file.txt", "config.json" (resolved against working directory)
-     */
-    path: string;
-    /**
-     * Content to write to the file.
-     */
-    content: string;
+	/**
+	 * Path where the file should be written.
+	 * - Absolute paths: "/app/.env", "/etc/config/app.conf"
+	 * - Tilde expansion: "~/.config/app.json" (expands to home directory)
+	 * - Relative paths: "./file.txt", "config.json" (resolved against working directory)
+	 */
+	path: string;
+	/**
+	 * Content to write to the file.
+	 */
+	content: string;
 }
 export interface SentryLike {
-    captureException: (error: unknown) => void;
+	captureException: (error: unknown) => void;
 }
 export interface ApplyFileOverridesResult {
-    success: boolean;
-    appliedFiles: string[];
-    failedFiles: Array<{
-        path: string;
-        error: string;
-    }>;
+	success: boolean;
+	appliedFiles: string[];
+	failedFiles: Array<{
+		path: string;
+		error: string;
+	}>;
 }
 /**
  * Expand tilde (~) in file path to home directory
@@ -35,7 +35,10 @@ export declare function expandTildePath(filePath: string): string;
  * @param workingDirectory - Optional working directory for resolving relative paths
  * @returns Resolved absolute path
  */
-export declare function resolveFilePath(filePath: string, workingDirectory?: string): string;
+export declare function resolveFilePath(
+	filePath: string,
+	workingDirectory?: string,
+): string;
 /**
  * Validate that a file path can be resolved to an absolute path
  * Supports tilde (~) expansion and relative paths (when workingDirectory is provided)
@@ -43,7 +46,10 @@ export declare function resolveFilePath(filePath: string, workingDirectory?: str
  * @param workingDirectory - Optional working directory for resolving relative paths
  * @returns true if valid, false otherwise
  */
-export declare function isValidFilePath(filePath: string, workingDirectory?: string): boolean;
+export declare function isValidFilePath(
+	filePath: string,
+	workingDirectory?: string,
+): boolean;
 /**
  * Apply multiple file overrides to the filesystem.
  * This function will:
@@ -58,7 +64,11 @@ export declare function isValidFilePath(filePath: string, workingDirectory?: str
  * @param sentry - Optional Sentry instance for error logging
  * @returns Object with overall success status and details for each file
  */
-export declare function applyFileOverrides(overrides: FileOverride[], workingDirectory?: string, sentry?: SentryLike): ApplyFileOverridesResult;
+export declare function applyFileOverrides(
+	overrides: FileOverride[],
+	workingDirectory?: string,
+	sentry?: SentryLike,
+): ApplyFileOverridesResult;
 /**
  * Read a file and return its content
  * Supports tilde (~) expansion and relative paths.
@@ -66,7 +76,10 @@ export declare function applyFileOverrides(overrides: FileOverride[], workingDir
  * @param workingDirectory - Optional working directory for resolving relative paths
  * @returns The file content or null if it cannot be read
  */
-export declare function readFileOverride(filePath: string, workingDirectory?: string): string | null;
+export declare function readFileOverride(
+	filePath: string,
+	workingDirectory?: string,
+): string | null;
 /**
  * Check if a file exists at the given path
  * Supports tilde (~) expansion and relative paths.
@@ -74,4 +87,7 @@ export declare function readFileOverride(filePath: string, workingDirectory?: st
  * @param workingDirectory - Optional working directory for resolving relative paths
  * @returns true if the file exists, false otherwise
  */
-export declare function fileOverrideExists(filePath: string, workingDirectory?: string): boolean;
+export declare function fileOverrideExists(
+	filePath: string,
+	workingDirectory?: string,
+): boolean;

package/types/cli/utils/git.d.ts

@@ -2,21 +2,33 @@ import type { DevToolsSys } from "../../types";
 import type { Credentials } from "../credentials";
 import type { GitConfigs } from "$/ai-utils";
 export interface RunCommandOptions {
-    cwd?: string;
-    debug?: boolean;
-    sys: DevToolsSys;
-    timeout?: number;
-    stdin?: string;
-    retry?: number;
+	cwd?: string;
+	debug?: boolean;
+	sys: DevToolsSys;
+	timeout?: number;
+	stdin?: string;
+	retry?: number;
 }
-type FetchGitConfigsResult = {
-    success: true;
-    gitConfigs: GitConfigs;
-} | {
-    success: false;
-    error: Error;
-};
-export declare function runCommand(cmd: string, args: string[], opts: RunCommandOptions): Promise<string>;
-export declare const isGitRepoCorrupted: (stdout: string, stderr: string) => boolean;
-export declare function fetchGitConfigs(credentials: Credentials, projectId: string): Promise<FetchGitConfigsResult>;
+type FetchGitConfigsResult =
+	| {
+			success: true;
+			gitConfigs: GitConfigs;
+	  }
+	| {
+			success: false;
+			error: Error;
+	  };
+export declare function runCommand(
+	cmd: string,
+	args: string[],
+	opts: RunCommandOptions,
+): Promise<string>;
+export declare const isGitRepoCorrupted: (
+	stdout: string,
+	stderr: string,
+) => boolean;
+export declare function fetchGitConfigs(
+	credentials: Credentials,
+	projectId: string,
+): Promise<FetchGitConfigsResult>;
 export {};

package/types/cli/utils/hosts-file-manager.d.ts

@@ -1,9 +1,9 @@
 export interface HostEntry {
-    hostname: string;
-    ip?: string;
+	hostname: string;
+	ip?: string;
 }
 export interface SentryLike {
-    captureException: (error: unknown) => void;
+	captureException: (error: unknown) => void;
 }
 /**
  * Check if a hostname is localhost or 127.0.0.1
@@ -20,7 +20,10 @@ export declare function isLocalhost(hostname: string): boolean;
  * @param sentry - Optional Sentry instance for error logging
  * @returns true if successful, false otherwise
  */
-export declare function updateHostsFile(entries: HostEntry[], sentry?: SentryLike): boolean;
+export declare function updateHostsFile(
+	entries: HostEntry[],
+	sentry?: SentryLike,
+): boolean;
 /**
  * Remove all managed entries from the hosts file
  * @param sentry - Optional Sentry instance for error logging

package/types/cli/utils/lock-file-example.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Example demonstrating the lock file conflict behaviors
+ *
+ * This script demonstrates three different conflict behaviors:
+ * - 'exit': Exits with code -10 if lock exists (default)
+ * - 'replace': Overwrites existing lock file
+ * - 'kill': Kills the existing process and overwrites lock file
+ *
+ * Usage:
+ * ```bash
+ * # Example 1: Exit behavior (default)
+ * # First run - creates lock file and waits
+ * ts-node lock-file-example.ts exit
+ * # Second run (in another terminal) - exits with code -10
+ * ts-node lock-file-example.ts exit
+ *
+ * # Example 2: Replace behavior
+ * # First run - creates lock file and waits
+ * ts-node lock-file-example.ts replace
+ * # Second run - replaces the lock file (first process still runs)
+ * ts-node lock-file-example.ts replace
+ *
+ * # Example 3: Kill behavior
+ * # First run - creates lock file and waits
+ * ts-node lock-file-example.ts kill
+ * # Second run - kills the first process and takes over
+ * ts-node lock-file-example.ts kill
+ * ```
+ */
+export {};

package/types/cli/utils/lock-file.d.ts

@@ -1,12 +1,12 @@
 import type { DevToolsSys } from "@builder.io/dev-tools/core";
 import type { FusionConfig } from "$/ai-utils";
 export interface LockFileData {
-    cwd: string;
-    projectId?: string;
-    branchId?: string;
-    pid: number;
-    createdAt: number;
-    port?: number;
+	cwd: string;
+	projectId?: string;
+	branchId?: string;
+	pid: number;
+	createdAt: number;
+	port?: number;
 }
 export type LockConflictBehavior = "replace" | "exit" | "kill";
 /**
@@ -25,4 +25,7 @@ export type LockConflictBehavior = "replace" | "exit" | "kill";
  * @param projectId - Optional project ID
  * @param branchId - Optional branch ID/name
  */
-export declare function registerLock(sys: DevToolsSys, fusionConfig: FusionConfig): Promise<void>;
+export declare function registerLock(
+	sys: DevToolsSys,
+	fusionConfig: FusionConfig,
+): Promise<void>;

package/types/cli/utils/parseGitDiff.d.ts

@@ -5,4 +5,7 @@ import type { ApplyActionsResult } from "../../../ai-utils/src/codegen";
  * @param includeFilesOnly - If true, only populate action and filePath properties
  * @returns Array of ApplyActionsResult objects
  */
-export declare function parseGitDiffToApplyActions(diff: string, includeFilesOnly?: boolean): ApplyActionsResult[];
+export declare function parseGitDiffToApplyActions(
+	diff: string,
+	includeFilesOnly?: boolean,
+): ApplyActionsResult[];

package/types/cli/utils/process-tracker.d.ts

@@ -1,4 +1,11 @@
-import { ChildProcess, type ChildProcessWithoutNullStreams, type ChildProcessByStdio, type SpawnOptions, type StdioPipe, type StdioNull } from "child_process";
+import {
+	ChildProcess,
+	type ChildProcessWithoutNullStreams,
+	type ChildProcessByStdio,
+	type SpawnOptions,
+	type StdioPipe,
+	type StdioNull,
+} from "child_process";
 import type { Readable } from "stream";
 import type { DevToolsSys } from "../../types";
 import type { DevCommandProcess } from "../launch/dev-server-orchestrator";
@@ -7,65 +14,81 @@ import type { DevCommandProcess } from "../launch/dev-server-orchestrator";
  * and ensures they are killed when the main process exits
  */
 declare class ProcessTracker {
-    private processes;
-    private cleanupHandlersRegistered;
-    constructor();
-    /**
-     * Register a spawned process for tracking and cleanup
-     */
-    track(childProcess: ChildProcess): void;
-    /**
-     * Untrack a process (useful if you're managing it manually)
-     */
-    untrack(childProcess: ChildProcess): void;
-    /**
-     * Kill all tracked processes
-     * @param sys - DevToolsSys for logging and Sentry integration
-     */
-    killAll(sys?: DevToolsSys): Promise<void>;
-    /**
-     * Register cleanup handlers for various exit signals
-     */
-    private registerCleanupHandlers;
-    /**
-     * Get the number of tracked processes
-     */
-    get count(): number;
+	private processes;
+	private cleanupHandlersRegistered;
+	constructor();
+	/**
+	 * Register a spawned process for tracking and cleanup
+	 */
+	track(childProcess: ChildProcess): void;
+	/**
+	 * Untrack a process (useful if you're managing it manually)
+	 */
+	untrack(childProcess: ChildProcess): void;
+	/**
+	 * Kill all tracked processes
+	 * @param sys - DevToolsSys for logging and Sentry integration
+	 */
+	killAll(sys?: DevToolsSys): Promise<void>;
+	/**
+	 * Register cleanup handlers for various exit signals
+	 */
+	private registerCleanupHandlers;
+	/**
+	 * Get the number of tracked processes
+	 */
+	get count(): number;
 }
 export declare const processTracker: ProcessTracker;
 /**
  * Options for trackedSpawn function
  */
 export interface TrackedSpawnOptions {
-    /** The command to run */
-    command: string;
-    /** Arguments for the command */
-    args?: readonly string[];
-    /** Spawn options */
-    options?: SpawnOptions;
+	/** The command to run */
+	command: string;
+	/** Arguments for the command */
+	args?: readonly string[];
+	/** Spawn options */
+	options?: SpawnOptions;
 }
 /**
  * Wrapper around child_process.spawn that automatically tracks the spawned process
  * and ensures it gets killed when the main process exits
  */
-export declare function trackedSpawn(config: TrackedSpawnOptions & {
-    options: SpawnOptions & {
-        stdio: "pipe" | [StdioPipe, StdioPipe, StdioPipe];
-    };
-}): ChildProcessWithoutNullStreams;
-export declare function trackedSpawn(config: TrackedSpawnOptions & {
-    options: SpawnOptions & {
-        stdio: [StdioNull | "ignore", StdioPipe, StdioPipe];
-    };
-}): ChildProcessByStdio<null, Readable, Readable>;
+export declare function trackedSpawn(
+	config: TrackedSpawnOptions & {
+		options: SpawnOptions & {
+			stdio: "pipe" | [StdioPipe, StdioPipe, StdioPipe];
+		};
+	},
+): ChildProcessWithoutNullStreams;
+export declare function trackedSpawn(
+	config: TrackedSpawnOptions & {
+		options: SpawnOptions & {
+			stdio: [StdioNull | "ignore", StdioPipe, StdioPipe];
+		};
+	},
+): ChildProcessByStdio<null, Readable, Readable>;
 export declare function trackedSpawn(config: TrackedSpawnOptions): ChildProcess;
-export declare function safeSpawn(shell: string, command: string, options: SpawnOptions & {
-    stdio: "pipe" | [StdioPipe, StdioPipe, StdioPipe];
-}): ChildProcessWithoutNullStreams;
-export declare function safeSpawn(shell: string, command: string, options: SpawnOptions & {
-    stdio: [StdioNull | "ignore", StdioPipe, StdioPipe];
-}): ChildProcessByStdio<null, Readable, Readable>;
-export declare function safeSpawn(shell: string, command: string, options: SpawnOptions): ChildProcess;
+export declare function safeSpawn(
+	shell: string,
+	command: string,
+	options: SpawnOptions & {
+		stdio: "pipe" | [StdioPipe, StdioPipe, StdioPipe];
+	},
+): ChildProcessWithoutNullStreams;
+export declare function safeSpawn(
+	shell: string,
+	command: string,
+	options: SpawnOptions & {
+		stdio: [StdioNull | "ignore", StdioPipe, StdioPipe];
+	},
+): ChildProcessByStdio<null, Readable, Readable>;
+export declare function safeSpawn(
+	shell: string,
+	command: string,
+	options: SpawnOptions,
+): ChildProcess;
 export declare const getTempFolder: () => string;
 export declare const cleanupTempFolder: () => boolean;
 /**
@@ -75,12 +98,23 @@ export declare const isMultiLineCommand: (command: string) => boolean;
 /**
  * Creates a temporary script file for multi-line commands
  */
-export declare const createTempScript: (command: string, shell: string) => string;
+export declare const createTempScript: (
+	command: string,
+	shell: string,
+) => string;
 export declare const getTempScriptPath: (extension: string) => string;
 /**
  * Cleans up a temporary script file
  */
 export declare const cleanupTempScript: (scriptPath: string) => void;
-export declare const getCommandWithShellArgs: (command: string, shell: string) => string[];
-export declare function killProcess(sys: DevToolsSys, procOrPid: ChildProcess | DevCommandProcess | number | undefined, abortSignal?: AbortSignal, timeout?: number): Promise<boolean>;
+export declare const getCommandWithShellArgs: (
+	command: string,
+	shell: string,
+) => string[];
+export declare function killProcess(
+	sys: DevToolsSys,
+	procOrPid: ChildProcess | DevCommandProcess | number | undefined,
+	abortSignal?: AbortSignal,
+	timeout?: number,
+): Promise<boolean>;
 export {};

package/types/cli/utils/repo-indexing-agent-prompt.d.ts

@@ -1 +1,2 @@
-export declare const REPO_INDEXING_AGENT_PROMPT = "# Design System Component Reference\n\nThis document provides a comprehensive overview of the design system's component architecture and available components for code generation and development reference.\n\n## System Architecture\n\nThe design system follows a modular component-based architecture where each component provides specific functionality. Components are organized into logical groups that can work independently or in combination with other components.\n\n### Component Organization Principles\n\n- **Single Responsibility**: Each component serves a specific purpose\n- **Composability**: Components can be combined to create complex interfaces\n- **Consistency**: All components follow the same design patterns and API conventions\n- **Accessibility**: Components are built with accessibility standards in mind\n\n## Documentation Structure\n\nFor detailed documentation on any component, refer to the corresponding MDX file in the `design-system-docs` folder. The documentation files follow the naming convention:\n\n```\ndesign-system-docs/[componentname].mdx\n```\n\nFor example:\n- `design-system-docs/button.mdx` - Detailed documentation for Button component\n- `design-system-docs/table.mdx` - Detailed documentation for Table component\n- `design-system-docs/annotationcontext.mdx` - Detailed documentation for AnnotationContext\n- `design-system-docs/applayout.mdx` - Detailed documentation for AppLayout component\n\nThese MDX files contain comprehensive information including:\n- Component API documentation\n- Usage examples\n- Props and configuration options\n- Best practices and implementation guidelines\n- Accessibility requirements\n- Integration patterns with other components\n\n## Components\n\n{{COMPONENTS}}\n{{ICONS}}\n{{TOKENS}}\n\n## Usage Guidelines\n\n### Component Dependencies\n- Most components are self-contained and can be used independently\n- Identify any components that require multiple components to work together\n- Some components work better in combination (e.g., Form + FormField, Table + Pagination)\n\n### Integration Patterns\n- Layout components typically serve as containers for other components\n- Form controls should be wrapped in FormField components for proper labeling\n- Navigation components can be used independently or as part of larger layout structures\n- Data display components can be enhanced with interactive elements like buttons and popovers\n\n### Accessibility Considerations\n- All components are built with accessibility in mind\n- Use semantic HTML structures provided by the components\n- Leverage built-in ARIA attributes and keyboard navigation\n- The LiveRegion component provides additional accessibility announcements when needed\n\n### Responsive Design\n- Layout components provide responsive behavior out of the box\n- Grid and ColumnLayout components adapt to different screen sizes\n- Mobile-friendly navigation patterns are built into navigation components\n\n## Usage Reference\n\nThis reference should be used to understand the available components and their intended purposes when generating code or building applications with this design system. For specific implementation details, always consult the corresponding MDX documentation file in the `design-system-docs` folder.";
+export declare const REPO_INDEXING_AGENT_PROMPT =
+	"# Design System Component Reference\n\nThis document provides a comprehensive overview of the design system's component architecture and available components for code generation and development reference.\n\n## System Architecture\n\nThe design system follows a modular component-based architecture where each component provides specific functionality. Components are organized into logical groups that can work independently or in combination with other components.\n\n### Component Organization Principles\n\n- **Single Responsibility**: Each component serves a specific purpose\n- **Composability**: Components can be combined to create complex interfaces\n- **Consistency**: All components follow the same design patterns and API conventions\n- **Accessibility**: Components are built with accessibility standards in mind\n\n## Documentation Structure\n\nFor detailed documentation on any component, refer to the corresponding MDX file in the `design-system-docs` folder. The documentation files follow the naming convention:\n\n```\ndesign-system-docs/[componentname].mdx\n```\n\nFor example:\n- `design-system-docs/button.mdx` - Detailed documentation for Button component\n- `design-system-docs/table.mdx` - Detailed documentation for Table component\n- `design-system-docs/annotationcontext.mdx` - Detailed documentation for AnnotationContext\n- `design-system-docs/applayout.mdx` - Detailed documentation for AppLayout component\n\nThese MDX files contain comprehensive information including:\n- Component API documentation\n- Usage examples\n- Props and configuration options\n- Best practices and implementation guidelines\n- Accessibility requirements\n- Integration patterns with other components\n\n## Components\n\n{{COMPONENTS}}\n{{ICONS}}\n{{TOKENS}}\n\n## Usage Guidelines\n\n### Component Dependencies\n- Most components are self-contained and can be used independently\n- Identify any components that require multiple components to work together\n- Some components work better in combination (e.g., Form + FormField, Table + Pagination)\n\n### Integration Patterns\n- Layout components typically serve as containers for other components\n- Form controls should be wrapped in FormField components for proper labeling\n- Navigation components can be used independently or as part of larger layout structures\n- Data display components can be enhanced with interactive elements like buttons and popovers\n\n### Accessibility Considerations\n- All components are built with accessibility in mind\n- Use semantic HTML structures provided by the components\n- Leverage built-in ARIA attributes and keyboard navigation\n- The LiveRegion component provides additional accessibility announcements when needed\n\n### Responsive Design\n- Layout components provide responsive behavior out of the box\n- Grid and ColumnLayout components adapt to different screen sizes\n- Mobile-friendly navigation patterns are built into navigation components\n\n## Usage Reference\n\nThis reference should be used to understand the available components and their intended purposes when generating code or building applications with this design system. For specific implementation details, always consult the corresponding MDX documentation file in the `design-system-docs` folder.";

package/types/cli/utils/sudo-helper.d.ts

@@ -0,0 +1,21 @@
+import type { DevToolsSys } from "@builder.io/dev-tools/core";
+/**
+ * Detects if a command contains "sudo"
+ * @param command The command string to check
+ * @returns true if the command contains "sudo", false otherwise
+ */
+export declare function detectSudoInCommand(command: string): boolean;
+/**
+ * Executes a command with sudo using sudo-prompt
+ * @param command The command to execute
+ * @param sys DevToolsSys instance for logging
+ * @returns Promise with the execution result
+ */
+export declare function executeSudoCommand(
+	command: string,
+	sys: DevToolsSys,
+): Promise<{
+	stdout: string;
+	stderr: string;
+	error?: Error;
+}>;

package/types/cli/utils/terminal-buffer.d.ts

@@ -3,27 +3,27 @@
  * to properly represent what would be shown in a real terminal
  */
 export declare class TerminalBuffer {
-    private lines;
-    private currentLine;
-    private currentColumn;
-    private maxLines;
-    private maxColumns;
-    private chunks;
-    constructor(maxLines?: number, maxColumns?: number);
-    write(data: string): void;
-    private ensureLineExists;
-    getWrite(): string;
-    getContent(): string;
-    clear(): void;
-    /**
-     * Get current cursor position for testing/debugging
-     */
-    getCursorPosition(): {
-        line: number;
-        column: number;
-    };
-    /**
-     * Get the current number of lines for testing/debugging
-     */
-    getLineCount(): number;
+	private lines;
+	private currentLine;
+	private currentColumn;
+	private maxLines;
+	private maxColumns;
+	private chunks;
+	constructor(maxLines?: number, maxColumns?: number);
+	write(data: string): void;
+	private ensureLineExists;
+	getWrite(): string;
+	getContent(): string;
+	clear(): void;
+	/**
+	 * Get current cursor position for testing/debugging
+	 */
+	getCursorPosition(): {
+		line: number;
+		column: number;
+	};
+	/**
+	 * Get the current number of lines for testing/debugging
+	 */
+	getLineCount(): number;
 }

package/types/cli/utils/workspace-path-resolver.d.ts

@@ -1,16 +1,19 @@
-import type { WorkspaceFolder, WorkspaceConfiguration } from "@builder.io/ai-utils";
+import type {
+	WorkspaceFolder,
+	WorkspaceConfiguration,
+} from "@builder.io/ai-utils";
 import type { DevToolsSys } from "../../types";
 export interface ResolveWorkspacePathOptions {
-    filePath: string;
-    forceWorkspace?: boolean;
-    workspace?: WorkspaceConfiguration;
-    workingDirectory: string;
-    sys: DevToolsSys;
-    canCollapseWorkspace?: boolean;
+	filePath: string;
+	forceWorkspace?: boolean;
+	workspace?: WorkspaceConfiguration;
+	workingDirectory: string;
+	sys: DevToolsSys;
+	canCollapseWorkspace?: boolean;
 }
 export interface ResolveWorkspacePathResult {
-    resolvedPath: string;
-    workspaceFolder?: WorkspaceFolder;
+	resolvedPath: string;
+	workspaceFolder?: WorkspaceFolder;
 }
 /**
  * Resolves a workspace file path to its actual file system path.
@@ -49,13 +52,15 @@ export interface ResolveWorkspacePathResult {
  * // }
  * ```
  */
-export declare function resolveWorkspacePath(options: ResolveWorkspacePathOptions): ResolveWorkspacePathResult;
+export declare function resolveWorkspacePath(
+	options: ResolveWorkspacePathOptions,
+): ResolveWorkspacePathResult;
 export interface AbsolutePathToWorkspaceUrlOptions {
-    absolutePath: string;
-    workspace?: WorkspaceConfiguration;
-    workingDirectory: string;
-    sys: DevToolsSys;
-    canCollapseWorkspace?: boolean;
+	absolutePath: string;
+	workspace?: WorkspaceConfiguration;
+	workingDirectory: string;
+	sys: DevToolsSys;
+	canCollapseWorkspace?: boolean;
 }
 /**
  * Converts an absolute file system path to a workspace URL if possible.
@@ -89,4 +94,6 @@ export interface AbsolutePathToWorkspaceUrlOptions {
  * // Returns: 'frontend/src/components/Button.tsx'
  * ```
  */
-export declare function absolutePathToWorkspaceUrl(options: AbsolutePathToWorkspaceUrlOptions): string | undefined;
+export declare function absolutePathToWorkspaceUrl(
+	options: AbsolutePathToWorkspaceUrlOptions,
+): string | undefined;

package/types/client/client-api.d.ts

@@ -1,12 +1,44 @@
-import type { ComponentRegistry, ConnectedBuilder, GetRegistryOptions, LaunchEditorFile, LoadComponentOptions, LocalConfig, RegisterComponentOptions, SetComponentInfoOptions, SetComponentInputOptions, UnregisterComponentOptions, ValidatedBuilder } from "../types";
-export declare const apiConnectBuilder: (publicApiKey: string, privateAuthKey: string, kind: string | null) => Promise<ConnectedBuilder>;
+import type {
+	ComponentRegistry,
+	ConnectedBuilder,
+	GetRegistryOptions,
+	LaunchEditorFile,
+	LoadComponentOptions,
+	LocalConfig,
+	RegisterComponentOptions,
+	SetComponentInfoOptions,
+	SetComponentInputOptions,
+	UnregisterComponentOptions,
+	ValidatedBuilder,
+} from "../types";
+export declare const apiConnectBuilder: (
+	publicApiKey: string,
+	privateAuthKey: string,
+	kind: string | null,
+) => Promise<ConnectedBuilder>;
 export declare const apiValidateBuilder: () => Promise<ValidatedBuilder>;
-export declare const apiLaunchEditor: (file: LaunchEditorFile) => Promise<unknown>;
-export declare const apiRegistry: (opts?: GetRegistryOptions) => Promise<ComponentRegistry>;
-export declare const apiLoadComponent: (opts: LoadComponentOptions) => Promise<ComponentRegistry>;
-export declare const apiRegisterComponent: (opts: RegisterComponentOptions) => Promise<ComponentRegistry>;
-export declare const apiSetComponentInfo: (opts: SetComponentInfoOptions) => Promise<ComponentRegistry>;
-export declare const apiSetComponentInput: (opts: SetComponentInputOptions) => Promise<ComponentRegistry>;
-export declare const apiUnregisterComponent: (opts: UnregisterComponentOptions) => Promise<ComponentRegistry>;
-export declare const apiDevToolsEnabled: (enabled: boolean) => Promise<ComponentRegistry>;
+export declare const apiLaunchEditor: (
+	file: LaunchEditorFile,
+) => Promise<unknown>;
+export declare const apiRegistry: (
+	opts?: GetRegistryOptions,
+) => Promise<ComponentRegistry>;
+export declare const apiLoadComponent: (
+	opts: LoadComponentOptions,
+) => Promise<ComponentRegistry>;
+export declare const apiRegisterComponent: (
+	opts: RegisterComponentOptions,
+) => Promise<ComponentRegistry>;
+export declare const apiSetComponentInfo: (
+	opts: SetComponentInfoOptions,
+) => Promise<ComponentRegistry>;
+export declare const apiSetComponentInput: (
+	opts: SetComponentInputOptions,
+) => Promise<ComponentRegistry>;
+export declare const apiUnregisterComponent: (
+	opts: UnregisterComponentOptions,
+) => Promise<ComponentRegistry>;
+export declare const apiDevToolsEnabled: (
+	enabled: boolean,
+) => Promise<ComponentRegistry>;
 export declare const apiLocalConfig: () => Promise<LocalConfig>;

package/types/client/edit-button/document-listeners.d.ts

@@ -1,2 +1,4 @@
 import type { BuilderDevToolsEditButton } from ".";
-export declare function initDocumentListeners(editButton: BuilderDevToolsEditButton): void;
+export declare function initDocumentListeners(
+	editButton: BuilderDevToolsEditButton,
+): void;

package/types/client/edit-button/index.d.ts

@@ -1,8 +1,8 @@
 export declare class BuilderDevToolsEditButton extends HTMLElement {
-    openInBuilder: HTMLAnchorElement | null;
-    block: HTMLElement | null;
-    constructor();
-    connectedCallback(): void;
-    show(contentElm: HTMLElement, blockElm: HTMLElement): string | null;
-    hide(): void;
+	openInBuilder: HTMLAnchorElement | null;
+	block: HTMLElement | null;
+	constructor();
+	connectedCallback(): void;
+	show(contentElm: HTMLElement, blockElm: HTMLElement): string | null;
+	hide(): void;
 }

package/types/client/menu/index.d.ts

@@ -1,5 +1,5 @@
 export declare class BuilderDevToolsMenu extends HTMLElement {
-    constructor();
-    connectedCallback(): void;
-    highlightOpener(): void;
+	constructor();
+	connectedCallback(): void;
+	highlightOpener(): void;
 }