@builder.io/dev-tools 1.10.13 → 1.10.15-dev.202508152043.0ab83c5da

package/types/cli/backup.d.ts

@@ -9,7 +9,6 @@ interface BackupGitRepoOptions {
     repoPath: string;
     aiBranch: string;
     featureBranch: string;
-    originalRepoUrl: string;
     workspace: WorkspaceConfiguration | undefined;
     debug: boolean;
 }
@@ -38,7 +37,7 @@ export type BackupGitRepoResult = BackupGitRepoResultValid | BackupGitRepoResult
  * The aiBranch is where the AI creates commits as work progresses, while featureBranch
  * is the base branch where work started (usually "main").
  */
-export declare function backupGitRepo({ sys, credentials, projectId, branchName, repoPath, aiBranch, featureBranch, workspace, originalRepoUrl, debug, }: BackupGitRepoOptions): Promise<BackupGitRepoResult>;
+export declare function backupGitRepo({ sys, credentials, projectId, branchName, repoPath, aiBranch, featureBranch, workspace, debug, }: BackupGitRepoOptions): Promise<BackupGitRepoResult>;
 interface InitialCommitHashResult {
     initialBranch: string;
     initialCommitHash: string;

package/types/cli/code-tools.d.ts

@@ -19,7 +19,6 @@ export interface FusionContext {
     git: boolean;
     gitRemote?: string;
     gitAutoInit?: boolean;
-    gitFeatureBranch?: string;
 }
 export interface ToolContext extends Partial<FusionContext> {
     sys: DevToolsSys;

package/types/cli/io-service.d.ts

@@ -0,0 +1,86 @@
+import { type SelectOptions, type ConfirmOptions, type TextOptions } from "@clack/prompts";
+import { spinner } from "./spinner";
+import type { WebSocket } from "ws";
+export interface IOService {
+    log(str: string): void;
+    info(str: string): void;
+    warn(str: string): void;
+    error(str: string): void;
+    write(text: string): void;
+    writeMetadata(metadata: Record<string, any>): void;
+    confirm(options: ConfirmOptions): Promise<boolean | symbol>;
+    text(options: TextOptions): Promise<string | symbol>;
+    select<Value>(options: SelectOptions<Value>): Promise<Value | symbol>;
+    createSpinner(): ReturnType<typeof spinner>;
+    isInteractive(): boolean;
+    isTTY(): boolean;
+    exit(code: number): Promise<void>;
+}
+export declare class ConsoleIOService implements IOService {
+    log(str: string): void;
+    info(str: string): void;
+    warn(str: string): void;
+    error(str: string): void;
+    write(text: string): void;
+    writeMetadata(_: Record<string, any>): void;
+    confirm(options: ConfirmOptions): Promise<boolean | symbol>;
+    text(options: TextOptions): Promise<string | symbol>;
+    select<Value>(options: SelectOptions<Value>): Promise<Value | symbol>;
+    createSpinner(): ReturnType<typeof spinner>;
+    isInteractive(): boolean;
+    isTTY(): boolean;
+    exit(code: number): Promise<void>;
+}
+export interface BaseMessage {
+    type: string;
+    [key: string]: any;
+}
+export interface LogMessage extends BaseMessage {
+    type: "log";
+    level: "info" | "warn" | "error";
+    message: string;
+}
+export interface WriteMessage extends BaseMessage {
+    type: "write";
+    text: string;
+}
+export interface SpinnerMessage extends BaseMessage {
+    type: "spinner";
+    status: "start" | "stop";
+    message: string;
+    code?: number;
+}
+export interface PromptRequest extends BaseMessage {
+    type: "prompt";
+    promptType: "text" | "confirm" | "select";
+    options: any;
+    requestId: string;
+}
+export interface PromptResponse extends BaseMessage {
+    type: "prompt_response";
+    requestId: string;
+    value: any;
+    cancelled?: boolean;
+}
+export declare class WebSocketIOService implements IOService {
+    private ws;
+    private promptCallbacks;
+    private messageQueue;
+    private isProcessing;
+    constructor(ws: WebSocket);
+    private sendMessage;
+    private prompt;
+    log(...args: any[]): void;
+    info(...args: any[]): void;
+    warn(...args: any[]): void;
+    error(...args: any[]): void;
+    write(text: string): void;
+    writeMetadata(metadata: Record<string, any>): void;
+    confirm(options: ConfirmOptions): Promise<boolean | symbol>;
+    text(options: TextOptions): Promise<string | symbol>;
+    select<Value>(options: SelectOptions<Value>): Promise<Value | symbol>;
+    createSpinner(): ReturnType<typeof spinner>;
+    isInteractive(): boolean;
+    isTTY(): boolean;
+    exit(code: number): Promise<void>;
+}

package/types/cli/launch/InitStateMachine.d.ts

@@ -24,6 +24,7 @@ export declare class InitStateMachine {
     checkout(branchName: string, ref: string, repoPath: string): Promise<boolean>;
     execAsync(exec: string, args: string[], cwd?: string): Promise<string>;
     git(args: string[], cwd?: string): Promise<string>;
+    performBackup(sys: DevToolsSys, credentials: Credentials, fusionConfig: FusionConfig, volumePath: string, repositories: Required<WorkspaceFolder>[]): Promise<void>;
     init(): Promise<boolean>;
     addInitLog(type: "status" | "log" | "error" | "complete", message: string, options?: {
         step?: InitStateStep;

package/types/cli/launch/helpers.d.ts

@@ -1,2 +1,14 @@
+import type { FusionConfig } from "$/ai-utils";
+import type { DevToolsSys } from "types";
 export declare const getCommandWithShellArgs: (command: string, shell: string) => string[];
 export declare const isInRemoteContainer: () => boolean;
+export declare const getVolumePath: (fusionConfig: FusionConfig) => string;
+export declare function computeAIBranchName(featureBranch: string, sessionId: string): string;
+export declare const getAndParseGitRepoInfo: ({ sys, gitWorkingDirectory, }: {
+    sys: DevToolsSys;
+    gitWorkingDirectory: string;
+}) => Promise<{
+    currentBranch: string;
+    featureBranch: string;
+    sessionId: string | undefined;
+}>;

package/types/cli/launch/install-jsx-plugin.d.ts

@@ -0,0 +1,7 @@
+import type { DevToolsSys } from "@builder.io/dev-tools/core";
+import { type InstallOutcome } from "./helpers";
+export declare const installJsxPlugin: (sys: DevToolsSys) => Promise<{
+    timestamp: string;
+    installOutcome: InstallOutcome;
+    error: string | undefined;
+}>;

package/types/cli/launch/logger.d.ts

@@ -0,0 +1,38 @@
+/**
+ * Initialize logging by wrapping all console methods to write to logs file
+ */
+export declare function initializeLogging(): void;
+/**
+ * Reset console methods to their original state
+ */
+export declare function resetLogging(): void;
+/**
+ * Display intro message with logging
+ */
+export declare const intro: (message: string) => void;
+/**
+ * Wrapped clack logging methods with file logging
+ */
+export declare const log: {
+    info: (message: string) => void;
+    success: (message: string) => void;
+    error: (message: string) => void;
+    warn: (message: string) => void;
+    step: (message: string) => void;
+    message: (message?: string, { symbol }?: import("@clack/prompts").LogMessageOptions) => void;
+    warning: (message: string) => void;
+};
+/**
+ * Display outro message with logging
+ */
+export declare const outro: (message: string) => void;
+/**
+ * Reads logs with pagination
+ * @param nextToken Line number to start reading from (0-indexed)
+ * @param limit Number of lines to read
+ * @returns Object containing logs array and next token
+ */
+export declare const readLogs: (nextToken?: number, limit?: number) => {
+    logs: string[];
+    nextToken: number | null;
+};

package/types/cli/launch-init-v2.d.ts

@@ -0,0 +1,13 @@
+import type { DevToolsSys } from "@builder.io/dev-tools/core";
+import type { CLIArgs } from "./index";
+export interface InitArgs extends CLIArgs {
+    repoFullName?: string;
+    branchName?: string;
+    githubToken?: string;
+    installCommand?: string;
+    dockerImageType?: "fusion-starter" | "node";
+}
+export declare function runLaunchInitCommandV2({ args, sys, }: {
+    sys: DevToolsSys;
+    args: InitArgs;
+}): Promise<number>;

package/types/cli/launch-init.d.ts

@@ -0,0 +1,19 @@
+import type { DevToolsSys } from "@builder.io/dev-tools/core";
+import type { CLIArgs } from "./index";
+export interface InitArgs extends CLIArgs {
+    repoFullName?: string;
+    branchName?: string;
+    githubToken?: string;
+    installCommand?: string;
+    volumePath?: string;
+    /**
+     * Indicates the type of docker image the CLI is running on.
+     *
+     * @default "node"
+     */
+    dockerImageType?: "fusion-starter" | "node";
+}
+export declare function runLaunchInitCommand({ args, sys, }: {
+    sys: DevToolsSys;
+    args: InitArgs;
+}): Promise<number>;

package/types/cli/repo-indexing/component-indexing.d.ts

@@ -12,13 +12,10 @@ export declare const processComponent: (sys: DevToolsSys, credentials: Credentia
     debug?: boolean;
     onIssue?: (issue: ComponentIssue) => void;
 }) => Promise<void>;
-export declare const processAgent: (sys: DevToolsSys, credentials: Credentials, sessionId: string, discoveredComponents: Component[], opts?: {
+export declare const processAgent: (sys: DevToolsSys, credentials: Credentials, discoveredComponents: Component[], opts?: {
     designSystemId?: string | null;
-    designSystemPackage?: string;
-    designSystemVersion?: string;
     retriesAllowed?: number;
     storeRepoIndexing?: boolean;
-    workspaceConfig?: WorkspaceConfiguration;
     debug?: boolean;
 }) => Promise<void>;
 export declare const deprecateObsoleteComponents: (credentials: Credentials, localComponents: Component[], remoteComponents: Component[]) => Promise<void>;

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

@@ -0,0 +1,2 @@
+import type { DevToolsSys } from "../core";
+export declare const parseDesignSystemVersion: (sys: DevToolsSys, designSystemPackage: string) => Promise<string | null | undefined>;

package/types/cli/repo-indexing.d.ts

@@ -0,0 +1,17 @@
+import type { DevToolsSys } from "../types";
+import type { CLIArgs } from "./index";
+export interface RepoIndexingDoc {
+    name: string;
+    content: string | {
+        name: string;
+        description: string;
+        components: string[];
+        relevantFiles: string[];
+    }[];
+    createdDate: string;
+    description: string;
+    id: string;
+    ownerId: string;
+    userId: string;
+}
+export declare const runRepoIndexing: (sys: DevToolsSys, args: CLIArgs) => Promise<void>;

package/types/cli/repo-indexing.mock.d.ts

@@ -0,0 +1,5 @@
+export declare const mockDeps: {
+    getStoredComponentDocs: () => Promise<never[]>;
+    storeComponentDocs: () => Promise<{}>;
+    runCodeGen: () => Promise<string>;
+};

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

@@ -1 +1 @@
-export declare const REPO_INDEXING_AGENT_PROMPT = "You are tasked with generating comprehensive documentation for a design system based on the provided components.\n\n---\n\n# 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## Component Categories\n\nCategorize and organize the components into logical groups such as:\n\n### Layout & Structure\nComponents that provide foundational layout and structural elements for applications.\n\n### Navigation\nComponents for user navigation and wayfinding within applications.\n\n### Form Controls\nInteractive components for user input and data collection.\n\n### Data Display\nComponents for presenting and organizing data and content.\n\n### Charts & Visualization\nComponents for data visualization and graphical representation.\n\n### Interactive Elements\nComponents for user interaction and actions.\n\n### Feedback & Communication\nComponents for providing feedback and communicating with users.\n\n### Form Organization\nComponents for structuring and organizing forms.\n\n### Content Organization\nComponents for organizing and structuring content.\n\n### Advanced Controls\nSpecialized components for complex interactions and data management.\n\n### Selection & Control\nComponents for user selections and interface controls.\n\n### Specialized Components\nComponents for specific use cases and advanced functionality.\n\n### Tutorial & Annotation System\nA specialized component group for creating interactive tutorials and annotations.\n\n### System Components\nComponents for system-level functionality and configuration.\n\n**Instructions for categorization:**\n1. Analyze each component provided below\n2. Group components by their primary functionality\n3. List each component with its description under the appropriate category\n4. Use the format: `**ComponentName** - [description from the component data]`\n5. Identify any component dependencies (like AnnotationContext)\n6. Create new categories if needed based on the actual component data\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.\n\n---\n\n**Template Usage Instructions:**\n1. Replace {{COMPONENTS}} with the actual JSON array of components\n2. Process each component to extract the name and description\n3. Categorize components based on their functionality and description\n4. Generate the appropriate category sections with component listings\n5. Ensure all component names are properly formatted and descriptions are included\n\nMake sure to save the output in the file AGENTS.md. You must use the Write tool in your response.";
+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\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/repo-indexing-group-prompts.d.ts

@@ -0,0 +1 @@
+export declare const REPO_INDEXING_GROUP_PROMPT: string;

package/types/common/ast/component-input-types.d.ts

@@ -17,7 +17,7 @@ export declare const NUMBER_TYPES: string[];
 export declare const BOOLEAN_TYPES: string[];
 export declare const ARRAY_TYPES: string[];
 export declare const OBJECT_TYPES: string[];
-export declare function getPrimitiveType(t: string): "number" | "string" | "boolean" | "object" | "array";
+export declare function getPrimitiveType(t: string): "string" | "object" | "number" | "boolean" | "array";
 export declare function removeQuotes(text: string): string;
 export declare const resolveType: (sys: DevToolsSys, checker: ts.TypeChecker, type: ts.Type) => string[] | undefined;
 export declare const typeToString: (sys: DevToolsSys, checker: ts.TypeChecker, type: ts.Type) => string;

package/types/common/ast/convert-values.d.ts

@@ -8,4 +8,4 @@ export declare function objectExpressionToObjectValue(sys: DevToolsSys, objectLi
 };
 export declare function convertArrayExpressionToJsArray(sys: DevToolsSys, arr: ts.ArrayLiteralExpression): any[];
 export declare function getTextOfPropertyName(sys: DevToolsSys, prop: ts.PropertyAssignment | ts.ObjectLiteralElementLike | undefined): string | undefined;
-export declare function valueToExpression(sys: DevToolsSys, val: any): ts.ObjectLiteralExpression | ts.Identifier | ts.StringLiteral | ts.NumericLiteral | ts.TrueLiteral | ts.FalseLiteral | ts.ArrayLiteralExpression;
+export declare function valueToExpression(sys: DevToolsSys, val: any): ts.ObjectLiteralExpression | ts.ArrayLiteralExpression | ts.Identifier | ts.StringLiteral | ts.NumericLiteral | ts.TrueLiteral | ts.FalseLiteral;

package/types/common/errors.d.ts

@@ -25,9 +25,8 @@ export declare class NetworkError extends PrivateError {
     readonly statusCode?: number;
     readonly errorCode?: string;
 }
-export type NetworkErrorType = "connection_refused" | "connection_timeout" | "dns_not_found" | "ssl_error" | "rate_limit" | "server_error" | "authentication_error" | "unknown";
+export type NetworkErrorType = "connection_refused" | "connection_timeout" | "dns_not_found" | "ssl_error" | "server_error" | "unknown";
 export declare function convertNodeErrorToNetworkError(error: Error & {
     code?: string;
 }, hostname: string, port?: number): NetworkError;
-export declare function createHttpError(statusCode: number, hostname: string, cause?: Error): NetworkError;
 export declare function displayNetworkError(error: NetworkError): void;

package/types/common/utils.d.ts

@@ -19,7 +19,7 @@ export declare function clone<T>(obj: T): T;
 export declare function shouldSkipFolder(sys: DevToolsSys, skipFolders: Set<string>, fileName: string): boolean;
 export declare function getPackageManager(): string;
 export declare function isWindows(): boolean;
-export declare function builderNpxPackage(): "\"@builder.io/dev-tools\"" | "builder.io";
+export declare function builderNpxPackage(): "builder.io" | "\"@builder.io/dev-tools\"";
 /**
  * Sanitizes a component name for use in filesystem paths by replacing invalid characters with underscores
  * @param name The component name to sanitize

package/types/core/adapters/vite/ensure-remix-config.d.ts

@@ -0,0 +1,6 @@
+import type { DevToolsSys } from "../..";
+import type { EnsureConfigResult } from "../../../types";
+/**
+ * Ensure the Remix Vite config has the necessary plugins and settings
+ */
+export declare function ensureRemixConfig(sys: DevToolsSys, configFilePath: string, configContent: string): Promise<EnsureConfigResult>;

package/types/core/adapters/vite/remix-utils.d.ts

@@ -0,0 +1,10 @@
+import type { DevToolsSys } from "../..";
+import type ts from "typescript";
+/**
+ * Check if the current project is using Remix framework
+ */
+export declare function isRemixFramework(sys: DevToolsSys): boolean;
+/**
+ * Update an object literal to include the external dependencies for Remix
+ */
+export declare function updateCommonJsLibrary(sys: DevToolsSys, config: ts.ObjectLiteralExpression): ts.ObjectLiteralExpression | null;

package/types/core/adapters/vite/vite-config-helpers.d.ts

@@ -0,0 +1,6 @@
+import type { DevToolsSys } from "../..";
+import type { EnsureConfigResult } from "../../../types";
+/**
+ * Update a Vite config file to include a plugin
+ */
+export declare function updateViteConfig(sys: DevToolsSys, configFilePath: string, configContent: string, pluginName: string, importPath: string): Promise<EnsureConfigResult>;