Release Compatibility
Use the exact dependency tuple tested and published with Better Convex Nuxt.
Better Convex Nuxt tests authentication and identity isolation as one dependency tuple. Treat exact peer versions as a security and behavior contract, not package-manager noise.
Version 0.6.1
| Dependency | Supported version |
|---|---|
| Node.js | ^22.12.0 || ^24.11.0 || >=26.0.0 |
| Nuxt | ^4.4.0 |
| Convex | 1.42.1 |
| Better Auth | 1.6.23 |
@convex-dev/better-auth | 0.12.5 |
The npm package metadata is the source of truth for the released tuple. This page documents version 0.6.1 and must change with the package.
Why versions are narrow
Authentication spans Better Auth cookies, its Convex adapter, token exchange, Nuxt request context, SSR serialization, and Convex clients. A semver-compatible-looking upgrade can alter one of those boundaries. The project expands ranges only after its contract, security, browser, and package-artifact checks pass.
Do not use package-manager overrides to silence peer conflicts in production. Upgrade the complete tuple and verify it, or remain on the published tuple.
Upgrade process
- Read every changelog entry between your current and target versions.
- Install the exact peer versions declared by the target package.
- Regenerate Convex types and rebuild Nuxt.
- Run type checks and application tests.
- Rehearse sign-in, sign-out, expiry, two-tab logout, account switching, SSR hydration, and reconnect.
- Verify enabled OAuth or recovery ceremonies against real provider infrastructure.
Pre-1.0 minor releases can contain deliberate hard cutovers. The project prefers one clear API over compatibility shims; plan upgrades accordingly.
Support evidence
A compiling app proves type compatibility, not operational compatibility. For security-sensitive deployment, review the repository security policy, changelog, and the exact package version you deploy.