Overview
Solid package setup and runtime API boundaries.
Solid package/runtime track: @better-auth-ui/solid owns provider wiring, Solid Query factories, mutation factories, and server helpers.
Use Zaidan when your job is installing copied Solid components or wiring TanStack Start app routes. Stay in this Solid section when your job is using package runtime APIs.
Quick path
- Install the Solid package and Solid Query.
- Create a Better Auth client with
createAuthClient. - Wrap your app with
AuthProviderand pass aQueryClient. - Use query and mutation option factories from
@better-auth-ui/solidin your components. - Use
@better-auth-ui/solid/serveronly at server boundaries that need server-side session data.
npm install @better-auth-ui/solid @tanstack/solid-query better-auth solid-jsPackage exports
| Export | Owns |
|---|---|
@better-auth-ui/solid | createAuthClient, AuthProvider, useAuth, auth config types, provider icons, query factories, mutation factories, and hooks such as useSession. |
@better-auth-ui/solid/server | Server-safe query helpers and auth server types for SSR boundaries. |
What belongs elsewhere
- Component installation, generated payloads, and copied-file ownership belong in Zaidan.
- TanStack Start app setup belongs in Zaidan integrations.
- Native Solid email templates are documented in Zaidan Email; React render-hook behavior and HeroUI React components are not Solid package APIs.
- Registry generation is part of the Solid example + Zaidan docs, not this package reference.
Next
Last updated on