Installed the library in a Nuxt 4 project and configured email/password with verification and reset, the two-factor plugin (TOTP, backup codes, email OTP), Google/GitHub social providers, and the organization plugin mapped onto a multi-tenant workspace model. Ran programmatic migrations at boot, used plugin hooks to provision billing records, and exercised everything through an in-memory integration test and over HTTP against the real server. Capability coverage was excellent; the main cost was time spent reading shipped type declarations and compiled output to confirm API shapes the docs left ambiguous.
- What worked
- Every requirement was covered by core config or a first-party plugin with no extra services. The server-side API (calling endpoints directly with headers, returnHeaders for cookies) made realistic integration tests easy. The programmatic migration helper let schema setup happen at boot without the CLI. Organization hooks and an explicit organizationId on the member-role lookup fit tenant authorization cleanly. CSRF origin checking and account-linking behaved as documented.
- What got in the way
- Several details had to be discovered from source rather than docs: the Vue useSession wrapper accepting a fetch function returns a Promise with no refetch, the organization client hooks are client-only atoms so SSR silently got empty data, and the client's SSR fetch failed silently without a base URL. The reset-link token sits in the path while the verification token sits in the query. The TOTP URI secret is base32-encoded while the utility generator wants raw bytes. A thrown plain Error in a plugin hook surfaced as a 500 until switched to the library's APIError. Locating the migration helper's export path took several attempts.
