@fonderie/vue-auth

@fonderie/vue-auth

Vue 3 composables for Fonderie auth — useLogin, useRegister, useSession, useLogout, useForgotPassword, useResetPassword, and useVerifyEmail. Thin bindings over @fonderie/client: reactive refs for loading/error/data state and the request itself, nothing else. Bring your own UI.

Install

npm install @fonderie/vue-auth

One client at the root (recommended)

Install the plugin from @fonderie/vue once (or call provideFonderie(client) in a root setup()) and every composable resolves the client by injection — no client argument at call sites:

import { FonderiePlugin } from "@fonderie/vue";

createApp(App).use(FonderiePlugin, client).mount("#app");

// in any component setup():
const { ...state } = useLogin();

Passing a client explicitly (as below) still works everywhere and takes precedence over injection — handy in tests and multi-client apps.

Use

<script setup>
import { FonderieClient } from '@fonderie/client';
import { useLogin, useSession } from '@fonderie/vue-auth';

const client = new FonderieClient({ baseUrl: 'https://api.example.com/v1' });
const { login, isLoading, error } = useLogin(client.auth);
const { user, isAuthenticated, logout } = useSession(client.auth);
</script>

<template>
  <button :disabled="isLoading" @click="login({ email, password })">
    {{ isLoading ? 'Signing in…' : 'Sign in' }}
  </button>
  <button v-if="isAuthenticated" @click="logout">Log out {{ user?.email }}</button>
</template>

Each composable takes the same AuthClient instance (client.auth) — construct one FonderieClient at the app root and pass it down (provide/inject or a prop). The access token is persisted to localStorage and restored automatically by useSession on setup; don't re-implement that in app code.

Want pre-built screens instead of wiring your own form? See @fonderie/vue-auth-screens.

Why this exists

You've shipped this plumbing before — auth, teams, billing, messaging — and the next project will ask for it again. Fonderie packages it once: plain TypeScript modules for @fonderie/core, PostgreSQL-backed, self-hosted, MIT. No external control plane, no per-seat anything. Register the modules you need; skip the ones you don't.

This package owns the Vue binding for auth — reactive state management around @fonderie/client, nothing more. No business logic lives here; it lives in @fonderie/auth on the server.

Browse the whole set at fonderiejs/fonderie · follow @fonderiejs

License

MIT © Fonderie, Inc.