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

@usecarte/components-core

v0.0.1

Published

Headless React behavior + provenance context + formatter/aggregation registry for Carte components. Components rendered outside a CarteRenderer throw CarteProvenanceError.

Downloads

18

Readme

@usecarte/components-core

Headless React behaviour, provenance context, and closed-enum formatter/aggregation registries for Carte components.

This package is what @usecarte/components is built on. Use it directly if you're authoring your own styled component package — it gives you the provenance plumbing, the formatter/aggregation registries, and the title-injection hook without prescribing a renderer or a styling system.

Install

pnpm add @usecarte/components-core @usecarte/core

React is an optional peer (>=18). Server-only consumers can import the React-free subpath:

import { FORMATTERS, AGGREGATIONS } from "@usecarte/components-core/registry";

What's in the box

  • <ProvenanceProvider> — wraps every panel with the receipt context. Components rendered outside a provider throw CarteProvenanceError (strict-throw, no silent fallback).
  • buildReceipt() — assembles an audit receipt from panel + transformations + context.
  • FORMATTERS, AGGREGATIONS — closed-enum registries the catalog/registry layers use to ensure receipts are statically auditable.
  • useInjectedTitle() — every default-catalog component pulls its title from the entry's titleTemplate rather than from an LLM-authored prop.
  • DevHarness — test-only wrapper that satisfies the provenance requirement without a full renderer.

Provenance is mandatory

A component from @usecarte/components rendered outside a <CarteRenderer> (or <ProvenanceProvider>, or <DevHarness> in tests) throws CarteProvenanceError. This is the load-bearing audit story — see the repo root README and the security model.

License

MIT