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/core

v0.0.10

Published

Core abstractions (Manifest, RenderContext, Helm, deps) for konfig.ts — typesafe Kubernetes + ArgoCD config in TypeScript.

Readme

@konfig.ts/core

The Kubernetes-agnostic primitives every other konfig.ts package builds on: the Manifest<A> carrier, the Dep.* kinds that drive compile-time dependency tracking, the Module factories, stable YAML, structural diff, a Helm integration with digest verification, and the render entrypoint.

Most projects reach for the higher-level packages (k8s, env, argocd) and touch core directly only for Helm.release, Dep.*, and Module.

Install

bun add @konfig.ts/core

Usage

Pull a digest-verified Helm chart inside a reusable module:

import { Application } from "@konfig.ts/argocd"
import { Dep, Helm, Module } from "@konfig.ts/core"
import { Namespace } from "@konfig.ts/k8s"

export const definePostgres = Module.fixedNs({
  target: Application.target,
  namespace: "data",
  build: ({ namespace }, opts: { storageGi: number }) => [
    Namespace.make({ name: namespace }),
    Helm.release({
      repo: "https://charts.bitnami.com/bitnami",
      chart: "postgresql",
      version: "16.0.0",
      digest: "sha256:…", // verified after pull AND on every cache hit
      namespace,
      values: { primary: { persistence: { size: `${opts.storageGi}Gi` } } }
    })
  ]
})

Inside a build, yield* Dep.Secret("ghcr-pull") records a typed dependency that another module must provide — the graph is checked when you compose everything at AppOfApps.entrypoint (see @konfig.ts/argocd).

Surface

| Area | Exports | | ----------- | ------------------------------------------------------------------------------------------------------------------------------- | | Manifest | Manifest (.make / .combine / .concat / .whenever / .embedYaml), render, renderManifest, RenderContext | | Deps | Dep.* kinds + Dep.provide* helpers; branded SecretRef / ConfigMapRef / PvcRef / ServiceAccountRef / BuiltImageRef | | Modules | Module.fixedNs, Module.dynamicNs | | Helm | Helm.release — chart pull + SHA-256 digest verification | | YAML & diff | Yaml.serialize / Yaml.filenameFor; diffFiles, formatDiff, parseYaml, redact | | Config | KonfigConfig, ImagesConfig, and their decoders | | Boundaries | boundary (Schema decode → BoundaryDecodeError); brand / unsafeCoerce escape hatches | | Errors | the tagged union AnyRenderError (HelmDigestMismatch, BoundaryDecodeError, …) |

Internals

Manifest<A> is only a recipe from a RenderContext to an Effect that produces an A — it does not track deps in its own type. Per-kind dependency tracking lives one level up, in the Effect Layers that Module and Application.define compose. See .docs/architecture.md.

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.