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

@linkbridge/sdk

v0.3.0

Published

Official Node.js / TypeScript SDK for the Linkbridge e-invoicing API.

Readme

@linkbridge/sdk

Official Node.js / TypeScript SDK for the Linkbridge e-invoicing API. Targets the OpenAPI contract at tools/openapi/openapi.yaml.

Requires Node ≥ 20.

Install

npm install @linkbridge/sdk

Quick start

import { LinkbridgeClient } from "@linkbridge/sdk";

const client = new LinkbridgeClient({
  baseURL: "https://api.linkbridge.ng",
  clientId: process.env.LB_CLIENT_ID!,
  clientSecret: process.env.LB_CLIENT_SECRET!,
});

const accepted = await client.invoices.submit({
  // canonical NRS invoice — see packages/schema/invoice.schema.json
  irn: "INV2024-SVC1-20240101",
  // ...
});
console.log("queued:", accepted.irn, "→", accepted.tracking_url);

Surface

| Area | Methods | | --------- | ------------------------------------------------ | | Invoices | client.invoices.submit / get / list | | Webhooks | client.webhooks.create / list | | Helpers | LinkbridgeClient.idempotencyKey() | | Webhook verifier | verifyWebhook(secret, body, header) | | Errors | LinkbridgeAPIError (status, code, traceId, …) |

The exhaustive generated type surface is available under @linkbridge/sdk/oapi for advanced use cases. The hand-curated types re-exported from the package root are the supported, semver-stable surface.

Authentication

Pass either:

  • clientId + clientSecret — the SDK performs OAuth2 client_credentials, caches the token, and refreshes it 60s before expiry.
  • staticToken — use a pre-issued OAuth access token and skip the SDK's client-credentials exchange.

Webhook verification

import { verifyWebhook, SIGNATURE_HEADER, WebhookVerificationError } from "@linkbridge/sdk";
import express from "express";

const app = express();
app.use(express.raw({ type: "application/json" })); // keep the raw body!

app.post("/webhook", (req, res) => {
  try {
    verifyWebhook(process.env.WEBHOOK_SECRET!, req.body, req.header(SIGNATURE_HEADER));
  } catch (err) {
    if (err instanceof WebhookVerificationError) return res.status(401).send(err.message);
    throw err;
  }
  // body is now trusted — JSON.parse and dispatch.
  res.sendStatus(204);
});

The verifier rejects requests outside a 5-minute clock skew window per spec §8.5.

Regenerating from the OpenAPI spec

./tools/scripts/codegen-sdk-node.sh

CI fails if regen produces a diff under src/oapi/ — this guarantees the SDK never drifts from the spec. See docs-internal/adr/0017-sdk-codegen-strategy.md.

Versioning

Semver. Breaking changes to the package-root surface require a major bump; the generated oapi/schema.gen.ts may evolve on any minor when the OpenAPI spec changes — pin the package if you depend on it directly.