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

@pxlhut/brand-editor

v0.1.1

Published

Headless React state for a brand settings screen that reshapes itself from the platform's control config.

Readme

@pxlhut/brand-editor

Headless React state for a brand settings screen that reshapes itself from the platform's control config — plus a shadcn-registry <BrandEditor /> UI built on top of it.

Part of Brandrail — multi-tenant brand theming with a per-field control-tier model the platform vendor owns. See the main README for the full pitch and the other three packages.

npm install @pxlhut/brand-editor

The hook

import { useBrandEditor } from "@pxlhut/brand-editor";

const state = useBrandEditor({
  controlConfig, // per-field tiers — see the tier-model doc below
  initial, // the site's current BrandConfig
  onSave: (patch) => fetch("/api/brand/draft", { method: "POST", body: JSON.stringify(patch) }).then((r) => r.json()),
  onPublish: () => fetch("/api/brand/publish", { method: "POST" }).then((r) => r.json()),
});

// state.fields[id]        — per-field value, error, dirty, disabled, tier-aware
// state.preview           — live tokens + serialized CSS, no server round-trip
// state.canPublish        — false while any contrast violation is outstanding

No markup, no styling — React-only for v0.1 (the logic ports to Vue/Svelte cheaply, but no port exists yet). See tier-model.md for what controlConfig actually means.

The UI — distributed via the shadcn registry, not npm

<BrandEditor /> is not exported from this package's JS entry point. shadcn/ui components are meant to be copied into your project and restyled, not imported from a compiled library — so the component ships as a registry item instead:

npx shadcn add https://raw.githubusercontent.com/pxlhut/brandrail/main/packages/brand-editor/public/r/brand-editor.json

This copies real, editable source into components/brand-editor/ in your project. It imports useBrandEditor from this package as a normal dependency — restyling the UI never means forking the logic — and installs its shadcn primitive dependencies (button, input, select, slider, tabs, textarea, badge, alert, label) via the same command.

See registry/brand-editor/README.md for the full per-file breakdown of what gets installed.