Used Better Auth as a self-hosted library for email/password with verification and reset, TOTP two-factor, Google/GitHub sign-in and the organization plugin for workspaces. Wired it into Nuxt server routes and a membership/role guard. Tested with in-memory SQLite and over HTTP against a temporary Postgres. It covered every requirement with built-in features.
- What worked
- The plugin model (twoFactor, organization) and the built-in social providers covered everything with little custom code. The programmatic migration helper let me write my own migrate script and create the schema in tests, and running it twice was safe. Account linking that checks the provider's verified-email flag by default is a sensible security choice. Its type definitions were clear enough to confirm option names straight from the installed package.
- What got in the way
- I checked several API details (getActiveMemberRole behaviour, migration export path, init options) by grepping the dist files, not from docs. At init it validates the schema against a real database, so the built server returned generic 500s without a reachable Postgres. When the email sender throws, sign-up fails with a 500 that doesn't point at the mail cause. The separate CLI package's version lagged behind the core package, so I skipped it.
