veta_auth_kit

Flutter mirror of @vetaui/auth-kit: AuthStrategy + AuthCapabilities, auth organisms, and mobile-first capability-driven screens.

Atomic Design layering:

• VetaSignInForm is an organism: inputs, submit, secondary providers, loading, errors, and callbacks.
• VetaSignInPage is the flow-kit screen: it assembles owned screen layout + VetaSignInForm + AuthStrategy.
• Flow kits may compose molecules, organisms, and reusable templates, but a public template is not required. Promote a shell to template only when it is reusable outside that specific flow.
• Provider packages such as veta_auth_kit_firebase and veta_auth_kit_supabase implement the strategy adapter.

Setup

import 'package:veta_foundations/veta_foundations.dart';
import 'package:veta_auth_kit/veta_auth_kit.dart';

void main() {
  configureVeta({'auth': mockAuthStrategy()});
  runApp(const MyApp());
}

Use VetaSignInPage for generated app screens, or VetaSignInForm only when a custom layout already owns the screen shell. Call getAuthCapabilities() before optional API methods — unsupported calls throw AuthKitNotSupportedException.

Strategies

Custom backends: extend AuthStrategy, override supported methods; leave the rest as defaults (they throw).

Fixtures

shared/fixtures/auth/sessions.json documents sample session rows aligned with the mock strategy seed data.

Dependencies

Backend SDKs live in sibling adapter packages. Generated Firebase apps should depend on both veta_auth_kit and veta_auth_kit_firebase; the default login surface is username/email + password unless the product spec explicitly enables another provider.