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

@faable/sdk-base

v1.5.2

Published

<p align="center"> <a href="https://faable.com"> <h1 align="center">SDK Builder base code</h1> </a> <p align="center">Build SDK Clients for Faable APIs</p> </p>

Readme

Install

 npm install @faable/sdk-base

Building an API client

Extend FaableApi and call the static create factory:

import { FaableApi } from "@faable/sdk-base";
import type { ApiParams } from "@faable/sdk-base";

export class MyApi extends FaableApi {
  constructor(params?: ApiParams) {
    super({ baseURL: "https://api.example.com", ...params });
  }
  getThing(id: string) {
    return this.fetcher.get(`/thing/${id}`);
  }
}

Authentication (pluggable, Octokit-style)

Auth is explicit — strategies never read environment variables. You pick an authStrategy and pass its config in auth; the chosen strategy drives the type of auth, so the editor autocompletes the right fields and rejects the wrong ones.

import { authClientCredentials, authApikey } from "@faable/sdk-base";

// client_credentials — the DEFAULT strategy. `auth` requires
// { client_id, client_secret }.
const api = MyApi.create({
  baseURL: "https://my-account.auth.faable.link",
  authStrategy: authClientCredentials,
  auth: { client_id: "...", client_secret: "..." },
});

// api key — `auth` requires { apikey }.
const api2 = MyApi.create({
  baseURL: "https://api.example.com",
  authStrategy: authApikey,
  auth: { apikey: "fak_xxx" },
});

authClientCredentials requests its token from <baseURL>/oauth/token by default. When the API host is not the auth server, point the token request at the right host with auth.domain:

auth: { client_id: "...", client_secret: "...", domain: "https://auth.example.com" }

Writing a custom strategy

A strategy is a builder (config, context) => { headers() }:

import type { AuthStrategyBuilder } from "@faable/sdk-base";

type BearerConfig = { token: string };

export const authBearer: AuthStrategyBuilder<BearerConfig> = (config) => {
  if (!config?.token) throw new Error("authBearer: `auth.token` is required");
  return {
    headers: async () => ({ authorization: `Bearer ${config.token}` }),
  };
};

context carries the api's domain (its baseURL) and debug flag, so a token-minting strategy can reach the auth server without extra config.