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

@forsyteco/leap-client-typescript

v0.1.3

Published

TypeScript LEAP API client generated with Hey API.

Readme

LEAP Client TypeScript

TypeScript LEAP API client generated from the LEAP OpenAPI (Swagger 2.0) definition using Hey API.

This package generates a single combined client at src/client/ and re-exports it from src/index.ts.

Install

npm install @forsyteco/leap-client-typescript

Usage (request-scoped)

import {
  createRequestScopedClient,
  exchangeAuthorizationCode,
  getApiV3Matters,
  requestWithResponse,
  refreshToken,
} from "@forsyteco/leap-client-typescript";

const exchanged = await exchangeAuthorizationCode({
  tokenUrl: process.env.LEAP_TOKEN_URL!,
  clientId: process.env.LEAP_CLIENT_ID!,
  clientSecret: process.env.LEAP_CLIENT_SECRET!,
  code: authCodeFromCallback,
  redirectUri: process.env.LEAP_REDIRECT_URI!,
});

const refreshed = await refreshToken({
  tokenUrl: process.env.LEAP_TOKEN_URL!,
  clientId: process.env.LEAP_CLIENT_ID!,
  clientSecret: process.env.LEAP_CLIENT_SECRET!,
  refreshToken: exchanged.refresh_token!,
});

const scoped = createRequestScopedClient({
  baseUrl: process.env.LEAP_BASE_URL!,
  auth: refreshed.access_token!,
  apiKey: process.env.LEAP_PUBLIC_API_KEY!,
});

const response = await getApiV3Matters({
  client: scoped.client,
  headers: scoped.headers,
  query: { maxItems: "20", isCurrent: "true" },
  throwOnError: true,
});

const uploadResponse = await requestWithResponse(scoped, {
  method: "POST",
  url: "/api/v1/documents",
  body: { matterId: "matter-1", docName: "example.pdf" },
});

console.log(uploadResponse.status, uploadResponse.data);

Use createRequestScopedClient() per request to avoid request-path reliance on shared mutable singleton auth/baseUrl configuration.

Development

npm install
npm run generate
npm run lint
npm run build

Regenerate Client

npm run generate

The generation flow:

  1. Downloads and validates the UK LEAP Swagger 2.0 spec from LEAP_SPEC_URL (openapi/manifest.ts) into openapi/openapi.json.
  2. Runs Hey API once to produce the combined client at src/client/.

Generated clients are treated as build artifacts. Re-run generation whenever LEAP updates the published Swagger definition.

Publish Checklist

npm run generate
npm run pack:check
npm run publish:public

prepack runs automatically during pack/publish, so lint/build happen before publishing without committing dist.

Release Commands

# choose one semantic version bump
npm run release:patch
npm run release:minor
npm run release:major

CI Publish (npm token)

Set NPM_TOKEN in your CI secret store, then run:

npm ci
npm run generate
npm run lint
npm run build
npm run pack:check
npm run publish:public