builder.io 1.11.50 → 1.12.0

package/types/cli/credentials.d.ts

@@ -50,3 +50,4 @@ export declare function getFigmaAuth(sys: DevToolsSys): Promise<FigmaAuth>;
 export declare function getBuilderCodegenUsage(builderPublicKey: string, builderPrivateKey: string): Promise<BuilderCodegenUsage>;
 export declare function getBuilderAuth(sys: DevToolsSys, preferSpaceId?: string): Promise<BuilderAuth>;
 export declare function storeCredentials(sys: DevToolsSys, credentials: Credentials): void;
+export declare function clearCredentials(sys: DevToolsSys): boolean;

package/types/cli/index.d.ts

@@ -92,4 +92,6 @@ export interface CLIArgs {
     disableMcp?: boolean;
     /** Enable privacy mode for codegen */
     privacyMode?: boolean;
+    /** Clear all stored credentials (logout) */
+    reset?: boolean;
 }

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

@@ -11,6 +11,7 @@ export declare const processComponent: (sys: DevToolsSys, credentials: Credentia
     debug?: boolean;
 }) => Promise<void>;
 export declare const processAgent: (sys: DevToolsSys, credentials: Credentials, discoveredComponents: Component[], opts?: {
+    hasIcons?: boolean;
     designSystemId?: string | null;
     retriesAllowed?: number;
     debug?: boolean;

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

@@ -0,0 +1,23 @@
+import type { DevToolsSys } from "../../types";
+import type { Credentials } from "../credentials";
+import type { WorkspaceConfiguration } from "$/ai-utils";
+export declare const discoverIcons: (sys: DevToolsSys, credentials: Credentials, sessionId: string, opts?: {
+    designSystemPackage?: string;
+    workspaceConfig?: WorkspaceConfiguration;
+    debug?: boolean;
+}) => Promise<{
+    icons: string[];
+    usage: string;
+    hash: string | undefined;
+}>;
+export declare const processIcons: (credentials: Credentials, iconDiscovery: {
+    icons: string[];
+    usage: string;
+    hash?: string;
+}, opts: {
+    designSystemId: string;
+    sessionId: string;
+    debug?: boolean;
+    previousHash?: string | null;
+    force?: boolean;
+}) => Promise<boolean>;

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

@@ -2,6 +2,7 @@ import type { DevToolsSys } from "../../core";
 import { type Credentials } from "../credentials";
 import type { DesignSystem, GenerateUserMessage, WorkspaceConfiguration, StoreComponentDocsInput, UpdateDesignSystemInput, DesignSystemScope, DisplayDesignSystem } from "$/ai-utils";
 export declare const AGENT_FILE = "AGENTS.md";
+export declare const ICONS_FILE = "icons.md";
 export declare const REPO_INDEXING_FOLDER = "repo-indexing";
 export interface UserSettings {
     isAdminInOrganization: boolean;

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

@@ -2,7 +2,7 @@ import type { DevToolsSys } from "../../types";
 import type { CLIArgs } from "../index";
 import { type Credentials } from "../credentials";
 import type { Component } from "./types";
-export declare const displayComponentLibrarySummary: (components: Component[], indexedComponents: Component[], startTime: number, failedComponents: string[] | undefined, isForce: boolean | undefined, designSystemName: string, designSystemId?: string) => void;
+export declare const displayComponentLibrarySummary: (components: Component[], indexedComponents: Component[], startTime: number, failedComponents: string[] | undefined, isForce: boolean | undefined, designSystemName: string, designSystemId?: string, numIconsIndexed?: number) => void;
 export interface RepoIndexingDoc {
     name: string;
     content: string | {

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

@@ -1 +1 @@
-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.";
+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\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.";