@fonderie/client 0.21.0 → 0.22.0

package/dist/index.d.cts

@@ -105,6 +105,10 @@ interface ITokens {
     access: string;
     refresh: string;
 }
+/** What GET /auth/providers answers: the sign-in methods this API can honour. */
+interface IAuthProvidersResult {
+    providers: string[];
+}
 interface IRegisterResult {
     tokens: ITokens;
     user: IUserDTO;
@@ -745,6 +749,16 @@ declare class AuthClient {
     readonly mfa: MfaClient;
     constructor(http: HttpClient, tokens: TokenStore);
     setAccessToken(token: string | undefined): void;
+    /**
+     * Which sign-in methods this deployment can actually honour.
+     *
+     * Public — the login screen needs it before anyone has signed in. Ask the
+     * server rather than shipping a build-time flag: the flag stores the same
+     * fact twice and lets the two disagree, and the symptom is a user clicking
+     * a provider the server cannot complete and landing on the provider's own
+     * error page, which the app cannot explain.
+     */
+    providers(): Promise<IApiResponse<IAuthProvidersResult>>;
     register(input: IRegisterInput): Promise<IApiResponse<IRegisterResult>>;
     login(input: ILoginInput): Promise<IApiResponse<ILoginResult | IMfaRequiredResult>>;
     appleNative(input: IAppleNativeInput): Promise<IApiResponse<ILoginResult>>;

package/dist/index.d.ts

@@ -105,6 +105,10 @@ interface ITokens {
     access: string;
     refresh: string;
 }
+/** What GET /auth/providers answers: the sign-in methods this API can honour. */
+interface IAuthProvidersResult {
+    providers: string[];
+}
 interface IRegisterResult {
     tokens: ITokens;
     user: IUserDTO;
@@ -745,6 +749,16 @@ declare class AuthClient {
     readonly mfa: MfaClient;
     constructor(http: HttpClient, tokens: TokenStore);
     setAccessToken(token: string | undefined): void;
+    /**
+     * Which sign-in methods this deployment can actually honour.
+     *
+     * Public — the login screen needs it before anyone has signed in. Ask the
+     * server rather than shipping a build-time flag: the flag stores the same
+     * fact twice and lets the two disagree, and the symptom is a user clicking
+     * a provider the server cannot complete and landing on the provider's own
+     * error page, which the app cannot explain.
+     */
+    providers(): Promise<IApiResponse<IAuthProvidersResult>>;
     register(input: IRegisterInput): Promise<IApiResponse<IRegisterResult>>;
     login(input: ILoginInput): Promise<IApiResponse<ILoginResult | IMfaRequiredResult>>;
     appleNative(input: IAppleNativeInput): Promise<IApiResponse<ILoginResult>>;

package/dist/index.js

@@ -242,6 +242,21 @@ var AuthClient = class {
     if (!token) this.http.clearCache();
   }
   // ── Public ─────────────────────────────────────────────────────────────────
+  /**
+   * Which sign-in methods this deployment can actually honour.
+   *
+   * Public — the login screen needs it before anyone has signed in. Ask the
+   * server rather than shipping a build-time flag: the flag stores the same
+   * fact twice and lets the two disagree, and the symptom is a user clicking
+   * a provider the server cannot complete and landing on the provider's own
+   * error page, which the app cannot explain.
+   */
+  providers() {
+    return this.http.request({
+      method: "GET",
+      path: "/auth/providers"
+    });
+  }
   register(input) {
     return this.http.request({
       method: "POST",