← All Releases
2.0.0
May 8, 2026Auth composables, proxied API requests, and automatic reCAPTCHA handling
Summary
- Added a full auth flow around
useAccAuth, including sign up, sign in, sign out, session switching, password reset, and current-user/session state sync. - Added the new
$apiplugin anduseAccApicomposable for backend requests through Accelerator's proxy layer. - Added automatic reCAPTCHA support across auth and API requests, documented in
useAccRecaptcha.
Added
- Added
useAccAuthplus the companion state composablesuseAccAuthSessions(),useAccActiveSessionId(), anduseAccAuthUser(). - Added the injected
$apiplugin and theuseAccApiwrapper for use inside pages, components, composables, and stores. - Added
useAccRecaptchaandcaptchaActionsupport so client requests can resolve a token automatically before sending. - Added the
/acc/proxy/[...path]proxy route for backend traffic and the/acc/authauth endpoints used by the auth composable. - Added auth-state resync and login-page redirect handling for
401and403responses through the$apiplugin. - Added automatic
captchaActiontocaptchaTokenresolution for proxied requests handled by$apianduseAccApi. - Added non-blocking upstream sign-out handling so local session cleanup can complete immediately.
- Added a centralized request pipeline for auth actions with shared error handling and automatic auth-state synchronization.
- Added proxy support for forwarding session tokens and refreshing expired access tokens before forwarding requests to the upstream API.
- Added a pluggable auth session storage model, including in-memory defaults and documented persistent storage options for development and production.
- Added docs for the new auth and API entry points:
useAccAuth,useAccApi,useAccRecaptcha, and$api.
Breaking Changes
- Backend calls are now expected to flow through the Accelerator proxy layer. If you were calling the old auth/backend paths directly, migrate to
$api,useAccApi, and the/acc/authauth endpoints used byuseAccAuth.