NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
A Flutter/Dart authentication client for the awesome-node-auth backend. Supports web (including WASM) via cookie + CSRF and native platforms via Bearer token.
Last release 4 months ago
20 May 2026
Too new to tell
only 2 release windows
Nearly every release is documented
notes for 7 of 7 stable releases
Nothing withdrawn
no release was ever pulled
5 months old
7 releases · first in 2026
One column per month.
Align client auth events and retry exclusions with awesome-node-auth v1.10 by @Copilot in #18
Full Changelog: v1.9.4...v1.10.0
cleanupSessions() — calls POST /auth/sessions/cleanup to prune expired/invalid sessions from the server store (closes section 7 of the v1.10 parity audit).getOAuthUrl(String provider) — returns the full OAuth redirect URL for a given provider (e.g. 'github', 'google'). Use this to initiate a redirect-based OAuth flow on web or open the URL in a webview/system browser on native.handleOAuthCallback() — picks up the authenticated session after a successful OAuth callback. Internally calls checkSession() and, on success, emits an AuthEventType.loggedIn event.awesome-node-auth backend v1.10.AuthClient API and auth.state.userStream.auth.checkSession() inside your AppLifecycleListener.onResume (or WidgetsBindingObserver.didChangeAppLifecycleState) to restore the session after the app returns to the foreground.intent-filter / iOS CFBundleURLTypes) to call auth.verifyMagicLink(token), auth.resetPassword(password, token), or auth.verifyEmail(token) as appropriate. For OAuth callbacks, call auth.handleOAuthCallback() once the redirect is complete.Doc fix: clarify that requestConflictLinkingEmail is a semantic alias of requestLinkingEmail with identical payload, and that the backend infers the c
requestConflictLinkingEmail is a semantic alias of requestLinkingEmail with identical payload, and that the backend infers the context from the presence or absence of a valid auth token in the request. The isConflict field is no longer sent in the request body, but if your backend version supports it, it is safely ignored if unused.Fixed auth/httpClient wrapper
Fixed auth/httpClient wrapper
Added example project with a simple Node.js backend and Flutter frontend demonstrating usage of the package.
README updated to give comprehensive usage instructions.
version bump to 1.9.0, aligned with awesome-node-auth backend v1.9.0
Initial public release, aligned with awesome-node-auth backend v1.8.5.
X-CSRF-Token header, same-origin only.TokenStorage.AuthState.userStream replays the current user to new subscribers immediately upon subscription.dart:html, no dart:io, no native plugins.Your coding agent can read these notes before it upgrades. Set up the MCP server →