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

@heynixie/pulumi-k8s

v0.70.1

Published

A Pulumi component that runs nixie on Kubernetes

Readme

A Pulumi component that runs nixie on Kubernetes.

The component registers nixie's StatefulSet, the web client and the backup job in one namespace, in the shape each nixie release ships. Each release of nixie publishes the component at its own version, so a deployment takes a change to that shape with a version bump. To start, install the package beside your Pulumi SDKs, call createNixie with your namespace and images, and point your ingress at the two Services it returns.

Install

The package ships an ES module with its type declarations, so a Pulumi program on Node or on Bun loads it. It takes @pulumi/pulumi 3 and @pulumi/kubernetes 4 as peer dependencies, which your program installs.

bun add @heynixie/pulumi-k8s

Features

  • nixie's pod. One replica on a ReadWriteOnce claim, with the configuration, the encrypted secrets and a git-sync container that follows your definitions repo on GitHub.
  • The web client. A Deployment that rolls out after nixie and calls its API by the Service.
  • The backup. A CronJob that runs the release's backup image on nixie's staging folder, and ships each snapshot set to your 2 restic repositories.
  • Moving onto it. Each resource keeps its own Pulumi name and an alias to the stack, so a stack that declared the same resources itself moves onto the component with no replacement.

Configuration

createNixie(name, args, opts) takes the per-deployment values in args, and their types in src/types.ts describe each one. Pass your Kubernetes provider in opts.

import { createNixie, nixieAPIPort, nixieWebPort } from '@heynixie/pulumi-k8s';

const nixie = createNixie(
  'nixie',
  {
    namespace: 'assistant',
    image: 'ghcr.io/zgeoff/nixie:<version>@sha256:<digest>',
    web: { image: 'ghcr.io/zgeoff/nixie-web:<version>@sha256:<digest>' },
    config: configText,
    secretsFile: sopsFileText,
    ageKey: ageKeySecret,
    definitions: { repository: '<owner>/<repo>', ref: 'live', deployKey: deployKeySecret },
    storageClassName: 'local-path',
  },
  { provider: cluster },
);

Documentation

The Kubernetes architecture covers the shape.