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

@configbutler/krm-stream

v0.2.1

Published

Receive live Kubernetes resource updates in browser apps and three-way merge them with form edits.

Readme

@configbutler/krm-stream

@configbutler/krm-stream is the official dependency-free ESM client for consuming a KRM resource stream in a browser or JavaScript application. It provides:

  • LiveResourceStore for server state, local drafts, conflicts, redactions, and merge patches.
  • connectWithEventSource for same-origin browser streams.
  • connectResourceStream for fetch-based transports with explicit headers.
  • resourceStreamURL for the v1 scope query format.

The package is headless and does not choose a UI framework. It works with the Go gateway in this repository or any conforming producer.

import { LiveResourceStore, connectWithEventSource, resourceStreamURL } from "@configbutler/krm-stream";

const store = new LiveResourceStore();
connectWithEventSource(
  resourceStreamURL("/resource-stream/v1", { version: "v1", resource: "configmaps", namespace: "app" }),
  store,
);

Vendoring it without a bundler

The default entry point is the per-module build: dist/index.js imports ./store.js, which imports ./merge.js, and so on. A bundler resolves that graph and tree-shakes it, and a browser resolves it at runtime, so every file has to be there.

If you have no bundler and no node_modules — you copy the library in and serve it yourself — import the flattened build instead. Same public API, one file, no relative imports left to resolve:

import { LiveResourceStore } from "@configbutler/krm-stream/bundle";

Vendored, that is one file to copy (dist/krm-stream.js) and one path to serve:

import { LiveResourceStore, connectWithEventSource } from "/krm-stream/krm-stream.js";

Both entry points are built from the same source and are exercised by the same browser test suite against a real EventSource. Neither has a runtime dependency.

Status

The unscoped krm-stream package is a compatibility forwarder. This project is pre-1.0: the protocol and the API may still change before 1.0. See the repository README, client state model, and release guide.