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

@donkeylabs/core

v0.1.0

Published

Core utilities, type-safe API definitions, and client SDK for donkeylabs packages

Readme

core

Shared TypeScript primitives that keep the backend and frontend in sync. The package exposes Zod-based route definitions, reusable error classes, JWT helpers, and an API client implementation that understands every route exposed by the ERP API.

Contents

packages/core
├── src/
│   ├── client/            # API client & persistence helpers
│   ├── dates/             # Moment-backed date utilities for UI formatting
│   ├── errors/            # Typed API error factory with HTTP status helpers
│   ├── formatting/        # UI format helpers shared by marketing sites
│   ├── interfaces/        # Route & rate limit abstractions
│   ├── jwt/               # JWT decoding + session normalization
│   ├── routes/            # Zod RouteDefinition instances for every API router
│   └── types/             # Shared TypeScript & Zod schemas
└── index.ts               # Barrel export + base URL/date helpers

Key exports:

  • RouteDefinition & RouterDefinition – Express-agnostic abstractions used by the API server and the API client to validate input/output and attach metadata such as permissions and rate limits.【F:packages/core/src/interfaces/server/route.ts†L1-L89】【F:packages/core/src/routes/auth/index.ts†L1-L94】
  • APIErrors – Centralized error factory that converts backend failures into serialized responses (and vice versa) so that UIs can surface localized feedback.【F:packages/core/src/errors/index.ts†L1-L130】
  • APIClient – Fetch wrapper that automatically attaches tokens, refreshes sessions, handles PDFs, and translates JSON failures into ApiError instances.【F:packages/core/src/client/APIClient.ts†L1-L123】
  • Date helperstimeSinceNowString, getFullDateString, toUTC, and related functions for Spanish-localized formatting built on Moment.js.【F:packages/core/src/index.ts†L1-L39】

Scripts

| Command | Description | | --- | --- | | bun run lint | Formats with Prettier and fixes linting issues via ESLint. | | bun run test | Executes the Bun test suite for any utilities with coverage. |

Usage

Add core as a workspace dependency and import the primitives you need:

import { APIRequest, APIClient, authRouter } from "core";

const client = new APIClient("/api");
const { routeDef } = APIRequest.router("auth").route("browserAuthentication");
const response = await client.run({ routeDef, input: { username, otpCode } });

The same route definitions power server handlers:

import { authRouter } from "core";

router.handle("browserAuthentication", async (input, ctx) => {
  const session = await model.login(input, ctx);
  ctx.res.json(authRouter.routes.browserAuthentication.parseResponse(session));
});

When you add or modify API routes, update the corresponding files in src/routes so that server and client stay in sync.