Who It Is For

Better Convex Nuxt is a strong fit when Convex is your application backend and Nuxt is more than a client-side shell.

Choose it when

• You use Nuxt 4 and want Convex data during SSR.
• Primary page data should remain live after hydration.
• You want query, pagination, mutation, action, upload, and connection state as Nuxt composables.
• You want one maintained Nuxt + Convex + Better Auth path for humans, SSR, delegated agents, and MCP clients.
• Signing in, signing out, and switching users must not reuse identity-owned query state.
• Nitro routes, webhooks, or server middleware need request-scoped Convex calls.
• You prefer one opinionated runtime over assembling the integration in application plugins.

It can still fit when

• Your app is client-only but you want the higher-level composables and Better Auth coordination.
• Only some routes use SSR. Query options can select the lifecycle per call.
• Authentication is optional. Omit convex.auth for a Convex-only build without Better Auth runtime code.
• You occasionally need imperative calls. useConvex() exposes a stable query, mutation, action, and onUpdate handle.

Choose another path when

• You use Vue without Nuxt.
• You need to support Nuxt 3. The package peer is the exact tested Nuxt 4 version.
• You want the smallest possible wrapper around a raw Convex client.
• You need an authentication provider that the application will integrate directly and do not want Better Auth.
• Your architecture requires direct ownership of setAuth, clearAuth, or raw client teardown.
• You expect the integration package to provide product roles, permissions, billing, or organization workflows.

Supported baseline

The current source candidate declares this exact dependency tuple:

The package manifest is canonical. Stable publication remains blocked until a stable Better Auth 1.7 tuple exists and the independent release reviews pass.