npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@fonderie/react-auth

v0.7.0

Published

React hooks for Fonderie auth — thin bindings over @fonderie/client.

Readme

@fonderie/react-auth

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

Install

npm install @fonderie/react-auth

One client at the root (recommended)

Wrap your app in FonderieProvider from @fonderie/react once and every hook resolves the client from context — no client argument at call sites:

import { FonderieProvider } from "@fonderie/react";

<FonderieProvider client={client}>
  <App />
</FonderieProvider>;

// anywhere below it:
const { ...state } = useLogin();

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

Use

import { FonderieClient } from '@fonderie/client';
import { useLogin, useSession } from '@fonderie/react-auth';

const client = new FonderieClient({ baseUrl: 'https://api.example.com/v1' });

function LoginForm() {
  const { login, isLoading, error } = useLogin(client.auth);

  return (
    <button
      disabled={isLoading}
      onClick={() => login({ email, password })}
    >
      {isLoading ? 'Signing in…' : 'Sign in'}
    </button>
  );
}

function Profile() {
  const { user, isAuthenticated, logout } = useSession(client.auth);
  if (!isAuthenticated) return null;
  return <button onClick={logout}>Log out {user?.email}</button>;
}

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

Want pre-built screens instead of wiring your own form? See @fonderie/react-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 React binding for auth — 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/sdk · follow @fonderiejs

License

MIT © Fonderie, Inc.