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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@thestartupfactory/van-gauth

v1.0.2

Published

The users of this library will interact through the Clients, created by calling {@link ByEmailPassword} or {@link ByToken}.

Downloads

14

Readme

Van-Gauth

The users of this library will interact through the Clients, created by calling {@link ByEmailPassword} or {@link ByToken}.

{@link ByToken} generates a set of auth primitives for authenticating users using a JWT, returning a {@link Clients.ByToken ByTokenClient}.

{@link ByEmailPassword} extends these to also allow authentication by email and password, returning a {@link Clients.ByEmailPassword ByEmailPasswordClient}.

Each requires a configuration containing both:

  • An object of callbacks {@link Connectors}, either {@link Connectors.ByEmailPassword} or {@link Connectors.ByToken} depending on the client you wish to use used internally within the library
  • Configuration settings, mainly optional, that cover items like Cookie names / Session Timeouts, etc.

Example Usage:

const parseClaims = iots.decode_to_result(claims);

const findUserByEmail = async (email: string): Promise<User | undefined> => {
  const result = await db.user.findUnique({
    where: { email },
  });
  return result ?? undefined;
};

const findUserByClaims = async (token: Claims): Promise<User | undefined> => {
  const result = await db.user.findUnique({
    where: { id: token.id },
  });
  if (!result) {
    return undefined;
  }
  return result;
};

const generateClaims = (user: User): Claims => ({
  id: user.id,
  email: user.email,
  role: user.role,
  status: user.status,
  plan: user.plan,
  featureFlags: user.featureFlags,
  notificationsEnabled: user.notificationsEnabled,
  activeBookId: user.activeBookId ?? undefined,
});

const updatePasswordByClaims = async (token: Claims, toStore: string) => {
  const updated_user = await db.user.update({
    data: { password: toStore, status: 'ACTIVE' },
    where: { id: token.id },
  });
  return updated_user;
};

const connector = {
  parseClaims,
  generateClaims,
  findUserByEmail: findUserByEmail(db),
  findUserByClaims: findUserByClaims(db),
  updatePasswordByClaims: updatePasswordByClaims(db),
};
const authClient = VG.ByEmailPassword({
  connector,
  jwt: {
    secret: config.jwt_secret,
  },
  cookie_name: COOKIE_NAME,
  session_timeout: SESSION_TIMEOUT,
});

// This client is then used throughout the application:
const result = await authClient.signInWithEmailAndPassword({
  email: '[email protected]',
  password: 'password123',
  cookieSetter: response,
});
if (result.success) {
  console.log('Yay, you are signed in.');
} else {
  console.error(`Failed to sign in: ${result.error.message}`);
}