/**
 * Component instance name resolution shared by the deploy and upload commands.
 *
 * 0.1.x mounted the component as `selfHosting`; 0.2.x defaults to
 * `staticHosting`. A same-name migration that kept the legacy instance name
 * would otherwise force `--component selfHosting` on every command, and the
 * penalty for forgetting it used to be a confusing "component not found" bail.
 * Instead the CLI probes both names when the caller relied on the default, and
 * warns when it lands on the legacy one.
 */
export declare const DEFAULT_COMPONENT_NAME = "staticHosting";
export declare const LEGACY_COMPONENT_NAME = "selfHosting";
/**
 * Instance names to probe, in order, for a requested name.
 *
 * Only the default request expands to include the legacy name. Any other
 * requested name is used verbatim: an explicit custom name must never be
 * silently redirected to a different instance.
 */
export declare function componentNameCandidates(requested: string): string[];
/**
 * Whether resolving `requested` to `resolved` was a legacy-name auto-detection
 * worth warning about. Only true when the caller relied on the default and we
 * fell back to the legacy name — an explicitly requested name (including a
 * command forwarding the resolved name to a subprocess) is left silent so a
 * single `deploy` warns at most once.
 */
export declare function isLegacyAutoDetected(requested: string, resolved: string): boolean;
/** Warning shown once when a command resolves to the legacy instance name. */
export declare function legacyComponentNameWarning(name: string): string;
//# sourceMappingURL=componentName.d.ts.map