[airowe]

Closes #135 (JS side).

Review the native PRs first. They carry the mechanism, and this one only forwards to them:

• feat(embedded): host-supplied footer below the login box frontegg-ios-swift#329
• feat(embedded): host-supplied footer below the login box frontegg-android-kotlin#290

This PR does not build until those land, because the bridges assign loginBoxFooter, which they add. As with #128, a native CI failure on loginBoxFooter is expected until then.

What

login() accepts a footer alongside themeOptions and localizations:

await login({
  localizations: { en: { loginBox: { login: { title: 'Sign-in' } } } },
  footer: {
    hideCaptchaBadge: true,
    rows: [
      { variant: 'body', segments: [
        { text: "Don't have an account? " },
        { label: 'Sign up now', url: 'myapp://sign-up' },
      ]},
      { variant: 'fine', segments: [
        { text: 'Protected by reCAPTCHA — ' },
        { label: 'Privacy Policy', url: 'https://policies.google.com/privacy' },
      ]},
    ],
  },
});

It is rendered below the login box's card, on its login screen only. This is the embedded-mode equivalent of boxFooter in @frontegg/react. The rationale is in #135.

Changes

• src/FronteggNative.ts: LoginBoxCustomization.footer, with LoginBoxFooter, LoginBoxFooterRow and LoginBoxFooterSegment types. The footer is sent through loginWithOptions with the same per-call semantics as the other two: omitted means null, which clears it. A footer also counts toward the "customization needs a newer native SDK" warning on old binaries.
• iOS bridge: FronteggApp.shared.loginBoxFooter = customization?["footer"]
• Android bridge: storage.loginBoxFooter = customization?.getMap("footer")?.toHashMap()
• docs/api.md: a footer row in the options table, plus a "Login box footer" section covering link handling and hideCaptchaBadge.

No new bridge method: loginWithOptions already takes the customization map, so a JS-only update against an older binary still signs in, and only the footer is dropped.

Tests

src/__tests__/index.test.tsx has 15 tests, all passing. There is a new case for forwarding a footer, and the existing expectations now include footer: null. A deliberate mutation that stops forwarding the footer is caught. tsc and eslint are clean on src.

🤖 Generated with Claude Code

---

Note

Medium Risk
Touches the login customization path and deep-link handling for footer URLs; behavior relies on companion native SDK changes until those ship.

Overview
Adds footer to login() options so embedded login can show structured content below the login card (parity with @frontegg/react’s boxFooter).

TypeScript defines LoginBoxFooter (rows of text/link segments, optional hideCaptchaBadge) and passes footer through existing loginWithOptions with the same per-call rules as theme/localizations: omitted fields become null and clear prior overrides. A non-null footer also triggers the “needs newer native SDK” fallback warning on old binaries.

iOS and Android bridges persist the payload via loginBoxFooter in applyLoginBoxCustomization. Docs document the option, link URL rules, and reCAPTCHA attribution. Tests assert footer forwarding and updated null-clearing expectations.

Depends on upstream native SDKs that implement loginBoxFooter rendering.

^{Reviewed by Cursor Bugbot for commit bc092d0. Bugbot is set up for automated code reviews on this repo. Configure here.}