npm better-auth 1.3.10-beta.3
v1.3.10-beta.3

latest releases: 1.4.8-beta.2, 1.4.8-beta.1, 1.4.7...
3 months ago

   🔄 Revert

   Why this was reverted

  • Cross-domain cookies are not reliable
    Modern browsers block 3rd-party cookies by default (Safari, Firefox, and Chrome without partitioned). Even when cookies are set, they are not accessible to the server in SSR contexts.
  • partitioned is Chrome-only
    The Partitioned flag works in some Chrome versions but is unsupported in other browsers, leading to inconsistent behavior.
  • Server access is broken
    Even if render.com sets a cookie for vercel.app, the Next.js server on vercel.app cannot read it. This causes SSR to fail, making the approach unsuitable for fullstack apps (works only for pure SPAs).
  • Misleading API/docs
    The current API suggested this was supported, but in reality the behavior is confusing and inconsistent.

   Workarounds

  • Use Next.js rewrites to proxy API calls so that both frontend and backend share the same parent domain.
  • Store tokens in localStorage (SPA only, SSR disabled).
  • Deploy frontend and backend under a shared domain (via Vercel, Render, or DNS like Cloudflare).
  • Remember: cross-site cookies will not work reliably in modern browsers.

   🐞 Bug Fixes

  • organization: Member and team hooks should apply on create organization  -  by @Bekacru in #4600 (7fc23)
    View changes on GitHub

Don't miss a new better-auth release

NewReleases is sending notifications on new releases.