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

@damatjs/deps

v0.6.0

Published

Dependencies for damatjs

Readme

@damatjs/deps

One place to pin and re-export every external runtime dependency shared across the Damat monorepo.

@damatjs/deps is a thin façade over the third-party libraries the framework relies on — Hono, Zod, Effect, pg, ioredis, nanoid, and uuid. Every other Damat package imports these through @damatjs/deps/<lib> instead of depending on the library directly. This gives the whole monorepo a single pinned version of each dependency, a single place to upgrade, and curated re-exports (for example, the hono subpath bundles the framework plus its commonly used sub-modules and @hono/node-server's serve).

Part of the Damat monorepo · Full guide · Internals

Install

bun add @damatjs/deps

Inside the monorepo it is referenced via the workspace protocol ("@damatjs/deps": "*"), so workspace packages always resolve the local copy.

When to use

Use it when:

  • You are writing a Damat package and need Hono, Zod, Effect, pg, ioredis, nanoid, or uuid. Import from @damatjs/deps/<lib> so you inherit the pinned version.
  • You want type-only imports (Context, MiddlewareHandler, Pool, RedisOptions, ...) from the same pinned source the rest of the framework uses.

Do not use it:

  • For dependencies that are not re-exported here (add those to your own package, or extend @damatjs/deps first).
  • As a way to mix versions — the point is that everyone shares the version pinned in this package's package.json.

Prefer the focused subpath imports (@damatjs/deps/zod) over the namespaced root import. The root @damatjs/deps exposes each library under a namespace (hono, zod, ...) to avoid name collisions; subpaths re-export flat.

Quick start

// Hono app + helpers, all from the pinned re-export
import { Hono, cors, serve } from "@damatjs/deps/hono";
import type { Context, MiddlewareHandler } from "@damatjs/deps/hono";

import { z } from "@damatjs/deps/zod";
import { nanoid } from "@damatjs/deps/nanoid";
import { Pool } from "@damatjs/deps/pg";

const app = new Hono();
app.use("*", cors());

const Body = z.object({ name: z.string() });

app.post("/users", async (c: Context) => {
  const data = Body.parse(await c.req.json());
  return c.json({ id: nanoid(12), ...data }, 201);
});

serve({ fetch: app.fetch, port: 3000 });

API

Each entry is a subpath export. Versions are pinned in this package's package.json.

| Export | Kind | Summary | | --- | --- | --- | | @damatjs/deps | namespace re-exports | Root entry. Re-exports every library under a namespace: hono, zod, effect, pg, ioredis, nanoid, uuid (e.g. import { zod } from "@damatjs/deps" then zod.z). Avoids name collisions; prefer the subpaths below. | | @damatjs/deps/hono | curated re-export | hono v4 (Hono, types like Context/MiddlewareHandler) plus hono/utils/http-status (ContentfulStatusCode, ...), hono/http-exception (HTTPException), hono/secure-headers (secureHeaders), hono/timing (timing), hono/cors (cors), and serve from @hono/node-server. | | @damatjs/deps/zod | re-export + alias | zod v4 (export * from "zod") plus a z named export (import { z } from "@damatjs/deps/zod") for v3-style ergonomics. | | @damatjs/deps/effect | re-export | effect v3 (export * from "effect"). | | @damatjs/deps/pg | re-export | node-postgres pg v8 (Pool, Client, ...). | | @damatjs/deps/ioredis | re-export | ioredis v5 (Redis, RedisOptions, ...). | | @damatjs/deps/nanoid | re-export | nanoid v5 (nanoid, customAlphabet, ...). | | @damatjs/deps/uuid | re-export | uuid v13 (v4, v7, ...). Also reachable via the root namespace (import { uuid } from "@damatjs/deps"). |

Pinned versions (package.json dependencies)

| Library | Pinned range | | --- | --- | | hono | ^4.12.0 | | @hono/node-server | ^1.13.7 | | zod | 4.3.6 (exact) | | effect | ^3.19.18 | | pg | ^8.21.0 | | ioredis | ^5.9.3 | | nanoid | ^5.1.6 | | uuid | ^13.0.0 |

How it fits

  • Dependencies: the external libraries listed above. No @damatjs/* runtime dependencies.
  • In-repo dependents: consumed by virtually every backend package. @damatjs/framework imports @damatjs/deps/hono, /nanoid, /zod; @damatjs/services and @damatjs/redis import /zod and /ioredis; ORM packages import /pg. It sits at the bottom of the dependency graph.

Documentation

License

MIT