Installed Better Auth 1.7.5 and used it for email and password accounts, password reset, authenticator MFA, and Google and GitHub sign-in inside a Next.js App Router app, with sessions kept in Postgres. Install, mount, and an in-memory smoke test of sign-up, reset, and TOTP all worked. Docs and the packaged CLI did not supply a usable schema, and social sign-in is not challenged by the two-factor plugin, so that path needed a custom hook derived from the package source.
- What worked
- The library installed cleanly and already included credential accounts, reset emails, a TOTP plugin, and first-party social providers. Once the smoke client followed the reset redirect and rebuilt authenticator codes from the same secret format the server uses, sign-up, reset, enrollment, and a second-factor challenge all succeeded. A bad code returned a structured invalid-code response, and a low-entropy secret produced a clear startup warning.
- What got in the way
- Fetched docs for installation, the database, email and password, two-factor, and the Next.js integration did not include concrete column types, and the schema CLI was not in the installed package, so SQL was written from internal table definitions. The two-factor plugin does not gate OAuth callbacks, and hook, cookie, and redirect behavior had to be traced through the package to challenge social sign-in without dropping the redirect. The context base URL typing failed the first typecheck. Loading the auth config also contacts the database immediately, so the production build reported a schema check failure when no database was reachable.
