import * as Effect from "effect/Effect"; import * as Option from "effect/Option"; import { Command } from "effect/unstable/cli"; import { CredentialsStore } from "../../Auth/Credentials.ts"; import { AlchemyProfile } from "../../Auth/Profile.ts"; /** * Populate an {@link AuthProviders} registry for display: the built-in * providers first, then the user's stack `providers()` layer on top so a * customized provider (same name) overrides the built-in one. Loading the * user's stack is best-effort — a missing or invalid entrypoint leaves the * built-ins in place. * * Registration happens as a side effect of building each layer (see * `AuthProviderLayer`), and later builds overwrite earlier entries by name, * so build order is what gives the user's providers precedence. */ export declare const collectAuthProviders: (options: { main: string; envFile: Option.Option; profile: string; }) => Effect.Effect<{ [providerName: string]: import("../../Auth/AuthProvider.ts").AuthProvider; }, import("effect/PlatformError").PlatformError, import("../../AlchemyContext.ts").AlchemyContext | AlchemyProfile | import("effect/unstable/process/ChildProcessSpawner").ChildProcessSpawner | CredentialsStore | import("effect/FileSystem").FileSystem | import("effect/Path").Path | import("effect/Scope").Scope>; export declare const profileCommand: Command.Command<"profile", {} | {}, {}, import("effect/PlatformError").PlatformError, import("../../AlchemyContext.ts").AlchemyContext | AlchemyProfile | import("effect/unstable/process/ChildProcessSpawner").ChildProcessSpawner | CredentialsStore | import("effect/FileSystem").FileSystem | import("effect/Path").Path | import("effect/Scope").Scope>; //# sourceMappingURL=profile.d.ts.map