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

@konfig.ts/docker

v0.0.10

Published

Workspace-graph-aware Dockerfile generator for konfig.ts monorepos.

Readme

@konfig.ts/docker

Workspace-graph-aware Dockerfile generator for konfig.ts monorepos. Write one declarative spec next to your app; the package resolves the app's transitive workspace closure and emits a production multi-stage Dockerfile and a dev single-stage one — no hand-maintained COPY lists.

Install

bun add -d @konfig.ts/docker

The app's package.json must set engines.<runtime> (e.g. engines.bun) — that's where the runner image tag comes from. Missing it is a hard error (EngineVersionMissing).

Usage

Author the spec at <app>/docker.ts:

import { Docker } from "@konfig.ts/docker"

export default Docker.app({
  target: "apps/api",
  runner: {
    production: true, // re-install prod-only deps for the closure
    workdir: "/app/apps/api",
    copy: [Docker.copy.workspaceSourceAll()], // keep workspace source for bun's export conditions
    expose: 8080,
    cmd: ["bun", "run", "src/main.ts"]
  },
  dev: { cmd: ["bun", "--watch", "src/main.ts"], expose: 8080 }
})

Generate the Dockerfiles, then build with the monorepo root as the Docker context (workspace COPYs only resolve from there):

konfig docker preview apps/api      # render to stdout
konfig docker write apps/api        # writes apps/api/Dockerfile + Dockerfile.dev
konfig docker diff apps/api         # non-zero exit if the on-disk files drifted

docker build -f apps/api/Dockerfile .

Production is a four-stage build (base → deps → builder → runner): deps installs from the full workspace set, builder copies only the target's closure and runs the build, runner is non-root, pinned to engines.<runtime>, and copies only what the spec declares. Dev is a single base → dev stage.

Spec atoms

| Family | Constructors | | -------------------- | ----------------------------------------------------------------------------------------------------- | | Docker.app | Docker.app(spec) — the spec entrypoint | | Docker.copy | builderArtifact(src, dst), workspaceSource(name), workspaceSourceAll(), path(src, dst, opts?) | | Docker.runtime | bun({ alpine? }), node({ alpine? }) — defaults from the PM; alpine defaults true | | Docker.pm | bun(), npm(), pnpm() — optional; auto-detected from the root package.json + lockfile | | Docker.build | script(name), command(argv), none() — defaults to script("build") if present | | Docker.healthcheck | httpGet({ path, port, … }), command(argv, opts?) | | Docker.user | nonRoot({ uid?, gid?, name? }), root() — a non-root user is injected if you omit one | | Docker.platform | linuxAmd64(), linuxArm64(), multi(values) |

Scope

Emits Dockerfiles only — no image building, pushing, tagging, or signing, and no BuildKit-specific syntax. yarn is not yet a supported PM. AnyDockerError is the discriminated union of failure modes (MonorepoRootNotFound, EngineVersionMissing, CircularWorkspaceDep, …).

Requirements

konfig.ts is built on Effect, currently in beta. Until Effect ships a stable 4.x, install the exact beta konfig.ts is built against:

  • [email protected] — required by every package.
  • @effect/[email protected] — required only when you call render() (the Node filesystem/subprocess entrypoint); manifest-only consumers can omit it (it is declared as an optional peer).

The pin is exact on purpose: Effect's beta line makes breaking changes between builds, so a looser range surfaces as ERESOLVE install conflicts. It relaxes to a caret range once Effect reaches a stable 4.x.