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

@zanii-id/react

v0.7.2

Published

Zanii ID login button for React — server-mode link, SPA public-client PKCE, opt-in popup sign-in

Readme

@zanii-id/react

The "Continue with Zanii ID" button for React applications.

npm install @zanii-id/react

Server-rendered apps (default)

The button is a plain link to your own backend's login route, which owns the OAuth flow and the client secret:

import { ZaniiLoginButton } from "@zanii-id/react";

<ZaniiLoginButton href="/auth/login" />

Single-page apps

For a true SPA with no backend, the browser acts as a public OAuth client and runs PKCE itself with WebCrypto:

<ZaniiLoginButton
  mode="spa"
  issuer="https://ids.zanii.agency"
  clientId="cli_..."
  redirectUri="https://app.example.com/callback"
/>

State and nonce live in sessionStorage, and sign-in is a full-page redirect — never a popup or an iframe.

The browser is a public client

The component throws if any prop looks like a credential:

<ZaniiLoginButton clientSecret="..." />   // throws immediately

A secret in browser code is a deployment mistake, so it fails loudly at development time rather than shipping.

Styling and accessibility

Renders a native <a> or <button>: real focus ring, 44px minimum target, aria-busy while redirecting, and an error slot. Style it with className or the exposed CSS variables — appearance is yours, security behaviour is not a prop.

import "@zanii-id/react/styles.css";

Finishing the SPA flow

useZaniiSpaAuth starts the flow; on the redirect page call completeZaniiSpaLogin to exchange the code as a public client (no secret, client_id in the body) and verify the id_token in the browser against the issuer's JWKS (RS256, issuer, audience, expiry, nonce):

import { completeZaniiSpaLogin } from "@zanii-id/react";

const { accessToken, claims } = await completeZaniiSpaLogin({ issuer, clientId, redirectUri });

Keep the tokens in memory only. A browser holds no refresh token; re-run login() when the access token expires.

Popup mode (opt-in)

Redirect is the default and the right choice almost always: the whole tab goes to the issuer, the user sees ids.zanii.agency in the address bar, and it works in every browser. Popup mode keeps your page mounted instead, which is worth it when the user is midway through something you would rather not unmount.

<ZaniiLoginButton
  mode="spa"
  popup                                   // opt in; omit for a redirect
  issuer="https://ids.zanii.agency"
  clientId="cli_..."
  redirectUri="https://app.example.com/auth/callback"
  onSignedIn={(session) => setUser(session.claims)}
/>

or from the hook:

const auth = useZaniiSpaAuth({ issuer, clientId, redirectUri, mode: "popup" });
const session = await auth.login();       // resolves when the popup hands the sign-in back

Your callback page serves both modes:

useEffect(() => {
  completeZaniiSpaLogin({ issuer, clientId, redirectUri })
    .then((session) => (isZaniiPopupCallback() ? publishZaniiPopupResult(session) : setUser(session)))
    .catch((err) => (isZaniiPopupCallback() ? publishZaniiPopupResult(err) : setError(err.message)));
}, []);

What it does about the awkward cases

| Case | Behaviour | |---|---| | The browser blocks the popup | falls back to a full-page redirect, so the user is never stuck. Pass onPopupBlocked="error" to surface it instead | | The user closes the window | login() rejects with PopupClosedError; nothing is left running | | Nobody finishes | PopupTimeoutError after five minutes (popupTimeoutMs), and the window is closed | | A mobile browser opens a tab and refuses to close it | after handing back the result the callback navigates to / (fallbackUrl) rather than stranding the user on a blank page | | Your app sends a Cross-Origin-Opener-Policy header | still works: the handoff rides a same-origin BroadcastChannel, not window.opener | | The browser has no BroadcastChannel | popup mode quietly becomes a redirect |

The result never leaves your origin: the popup lands on your redirect URI, so the channel carrying it is same-origin, and a message whose state is not the one this flow issued is ignored. Whichever mode you choose, the password, the second factor and the passkey happen on the issuer's own origin and your app only ever sees tokens it verified itself.

Licence

Apache-2.0. See LICENSE.