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

@rpcbase/auth

v0.104.0

Published

UI helpers + API routes for authentication.

Downloads

2,904

Readme

@rpcbase/auth

UI helpers + API routes for authentication.

1) Register auth routes in your API

Example (like sample-app):

import { initApi } from "@rpcbase/api"
import { routes as authRoutes } from "@rpcbase/auth/routes"

const routes = {
  ...authRoutes,
  ...import.meta.glob("./**/handler.ts"),
}

export const runApi = async ({ app }) => {
  await initApi({ app, routes })
}

The OAuth request (state + PKCE verifier) is stored server-side in RBOAuthRequest (global model). A short-lived HttpOnly cookie binds state to the initiating browser (SameSite=None; Secure on HTTPS). The callback handler uses an Express session only to sign the user in.

2) Configure providers

Provider configuration is provided by the host app (server-side) at runtime.

Call configureOAuthProviders() before initializing your API routes:

import { initApi } from "@rpcbase/api"
import { configureOAuthProviders } from "@rpcbase/auth/oauth"
import { routes as authRoutes } from "@rpcbase/auth/routes"

configureOAuthProviders({
  mock: {
    issuer: "http://localhost:9400",
    clientId: "rpcbase-sample-app",
    scope: "openid email profile",
    callbackPath: "/api/auth/oauth/mock/callback",
  },
})

const routes = {
  ...authRoutes,
  ...import.meta.glob("./**/handler.ts"),
}

export const runApi = async ({ app }) => {
  await initApi({ app, routes })
}

The app is responsible for sourcing secrets (env, vault, etc.) and passing them to configureOAuthProviders().

Each provider must define a scope and a callbackPath so the generated redirect_uri matches your routing:

configureOAuthProviders({
  google: {
    issuer: "https://accounts.google.com",
    clientId: process.env.GOOGLE_CLIENT_ID!,
    scope: "openid email profile",
    callbackPath: "/api/auth/oauth/google/callback",
  },
})

3) Start the OAuth flow from the client

window.location.assign("/api/auth/oauth/mock/start")

You can optionally pass a return path:

window.location.assign("/api/auth/oauth/mock/start?returnTo=/app")

Optional: declare OAuth routes yourself

If you don’t want to mount the full authRoutes, you can register the OAuth handlers manually:

import { createOAuthCallbackHandler, createOAuthStartHandler } from "@rpcbase/auth/oauth"

export default (api) => {
  api.get("/api/auth/oauth/:provider/start", createOAuthStartHandler({
    getAuthorizationParams: (providerId) =>
      providerId === "apple"
        ? { response_mode: "form_post" }
        : undefined,
  }))

  const callback = createOAuthCallbackHandler({
    createUserOnFirstSignIn: false,
    missingUserRedirectPath: "/auth/sign-up",
    successRedirectPath: "/app",
  })

  api.get("/api/auth/oauth/:provider/callback", callback)
  api.post("/api/auth/oauth/:provider/callback", callback)
}

4) What happens on callback

On a successful callback:

  • tokens are exchanged (/token)
  • userinfo is fetched (when supported by the provider)
  • the matching RBUser is created on first-seen identity (and the OAuth credentials are saved under RBUser.oauthProviders[provider])
  • the session is signed in, and the user is redirected to /onboarding

If the callback handler is configured with createUserOnFirstSignIn: false and no matching user is found, it redirects to missingUserRedirectPath (when provided).

Apple (helper)

Apple requires a JWT clientSecret. You can generate it server-side:

import { createAppleClientSecret } from "@rpcbase/auth/oauth"

Mock provider (dev/tests)

This repo uses oauth2-mock-server in sample-app/server.js to spin up a local OIDC provider for development and Playwright tests.

Notes:

  • oauth2-mock-server simulates auth and immediately redirects back on /authorize (it does not provide a UI to pick an account).
  • Override the port with RB_OAUTH_MOCK_SERVER_PORT (default 9400)