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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@lcdev/api-service

v0.1.6

Published

Common structure for calling API endpoints

Downloads

2

Readme

API Service

A tiny frontend library to help create a "service wrapper" over backend APIs. Helps track API tokens and boilerplate for API responses.

You write an 'AuthManager' class to keep track of the current logged in JWT token.

import { AuthManager, localStorage } from '@lcdev/api-service';

interface JWT { ... } // whatever your JWT contains

export class MyAuthManager extends AuthManager<JWT> {
  static async create() {
    const manager = new MyAuthManager(
      localStorage(), // where to store the token
      {
        // this is the key that's used in the above functions
        tokenKey: 'token-key',

        // when to automatically call refresh, in keepAlive
        refreshTokenWithinSeconds: 60 * 30,
      },
      {
        async refreshToken(currentToken) {
          // call an API, return back the jwt string
        },
        // optional - any errors trigger this callback
        error(err) { ... }
        // optional - any 401 errors trigger this callback
        unauthorized() { ... }
        // optional - when token has expired, this callback is triggered
        expiry() { ... }
      },
    );

    return manager.waitUntilReady();
  }
}

Your API calling service would look like this.

import { api } from '@lcdev/fetch';
import { ApiResponse, unwrapApiResponse } from '@lcdev/api-service';

export const createCoreApi = (baseURL: string, auth: MyAuthManager) => {
  const coreApi = api(baseURL)
    .withBearerToken(auth)
    // optional - logic to automatically keepAlive after every API request
    .onResponse(res => {
      if (!/\/auth\//.exec(res.url)) {
        auth.keepAlive().catch(() => {});
      }
    });

  // this is an object with calls to all endpoints of your API
  return {
    async login(username: string, password: string) {
      type Response = ApiResponse<ApiData.Token>;

      const response = await coreApi
        .post('/api/auth/login')
        .withBody({ username, password })
        .json<Response>();

      const { data } = unwrapApiResponse(response);

      return data;
    },
  } as const;
};