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

@schitzophrenic/auth-lib

v1.0.2

Published

This library provides a standardised approach to simple username + password authentication.

Readme

AuthLib

This library provides a standardised approach to simple username + password authentication.

Dependency

To use this service there needs to be an authorization backend with the following endpoints:

  1. (POST) {baseURL}/login ({username: string, password: string } -> Principal)
  2. (GET) {baseURL}/logout -> void
  3. (GET) {baseURL}/currentUser -> Principal

The Principal Responses shall fulfill this interface:

interface Principal {
  username: string,   // Alias of the user
  fullName: string,   // Full name of the user
  email: string,      // Email Address of the user
  appName: string,    // Name of your application
  authorities: Roles  // List containing roles
}

Notice: As roles the following values are supported: ADMIN, USER, TECHNICAL

Usage

To use the authentication, just add the feature "withPrincipal()" to you ngrx signal store.

This will add a check if a user is logged in to the onInit of your app on open a login dialog if the user is not logged in. This store also provides methods for handling login, logout and getting a current user.

Example

export const AppStore = signalStore(
  {providedIn: "root"},
  withPrincipal(),
  ...
);

In some other component or service, you can now read the principal as follows:

@Injectable({...})
export class MyService {
  private store = inject(AppStore);
  private myUser = this.store.principal();
  
  ...
  
  public logOut(): void {
    this.store.logout();
  }
  
  // Use this only if you do not want to use the provided login mask.
  public logIn(username: string, password: string): Observable<boolean> {
    return this.store.login(username, password);
  }
}

Configuration

There are three different configuration points for this library:

  1. You may call withPrincipal(false), if you no not wish to use the provided login dialog.
  2. You may use the provided authorizationInterceptor to configure your http client to forget the principal and try to open the login dialog if you use it.
  3. You may provide custom AuthorizationConfig as shown in the example below, to change that base url of your login service, add a frontend link to an endpoint where users may change their password and a backdropCssClass for the backdrop of the login dialog.
{
    provide: AuthenticationConfig,
    useValue: { 
        baseUrl: 'http://localhost:8081/auth', 
        resetPasswordLink: '/resetPassword', 
        backdropCssClass: 'solid' 
    }
}

Deactivation of Routes

If you do not want to have your store to load the current user, we provide a canActivate function principalDeactivatedGuard that can be added to routes to prevent them from calling the currentUser endpoint.