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

@gitkraken/api-tools

v0.2.0

Published

Validation-agnostic HTTP/auth transport for GitKraken client SDKs (token-per-request, envelope unwrapping).

Downloads

184

Readme

@gitkraken/api-tools

Validation-agnostic HTTP/auth transport for GitKraken client SDKs.

Transport wraps a host-injected request function (or a default globalThis.fetch requester), attaches a fresh bearer token per request, unwraps the identity-service { data, error } envelope, and surfaces non-2xx (and 3xx redirects) as a typed HttpError. Callers narrow the unwrapped data by passing an optional parse hook; the transport itself owns no schema library.

Install

pnpm add @gitkraken/api-tools

Usage

import { Transport, HttpError } from '@gitkraken/api-tools';

const transport = new Transport({
  baseUrl: 'https://id.gitkraken.com',
  getToken: async () => authStore.accessToken, // awaited per request
});

// `parse` runs on the unwrapped envelope data; bring your own validator (zod, etc.).
const { data, status, headers } = await transport.request({
  method: 'GET',
  path: '/v1/demographic',
  parse: (raw) => demographicSchema.parse(raw),
});

request<T> takes { method, path, body?, headers?, signal?, parse? } and resolves { data: T | undefined, status, headers }. data is undefined for a 204 or an empty JSON body (an empty body with a non-JSON content-type resolves ''); caller headers are merged over the defaults (Authorization, Content-Type: application/json).

Injecting your own request function

The host owns the network. Omit request to use the default fetch adapter, or pass one (same { body, status, headers } shape as GitKraken's other SDKs) for proxies, on-prem hosts, or custom TLS:

const transport = new Transport({
  baseUrl,
  getToken,
  request: async ({ method, url, headers, body, signal }) => {
    const res = await myHttp(method, url, { headers, body, signal });
    return { body: res.text, status: res.status, headers: res.headers };
  },
  logger: { debug: log.debug, warn: log.warn, error: log.error }, // optional
});

Errors

A non-2xx response, a 3xx redirect (not followed), a 2xx { data, error } envelope with a non-null error, or malformed JSON all reject with an HttpError:

try {
  await transport.request({ method: 'POST', path: '/v1/milestones', body });
} catch (err) {
  if (err instanceof HttpError) {
    // err.status, err.body (parsed when JSON), err.headers
  }
}

Responses

  • 204 / empty body (no or JSON content-type) → data: undefined.
  • Empty body typed non-JSON (e.g. text/plain) → ''.
  • JSON { data, error } → unwrapped data; an object without data/error keys is returned as-is; a non-JSON body is handed back untouched.
  • parse, when provided, runs last on the unwrapped value.