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

pluggable-react

v0.1.0

Published

Create React components that can be overridden globally or via context

Readme

pluggable-react

Create React components that can be overridden globally or via context. Useful for design systems, white-label apps, and dependency injection of UI.

Installation

npm install pluggable-react react

Usage

1. Create a pluggable component

Use createPluggable to define a component with a default implementation that can be swapped out. The first argument is a unique id used to look up overrides in the registry:

import { createPluggable } from "pluggable-react";

const DefaultButton = ({ label, onClick }: { label: string; onClick?: () => void }) => (
  <button type="button" onClick={onClick}>{label}</button>
);

export const Button = createPluggable("MyApp.Button", DefaultButton);
// Button.id === "MyApp.Button"

2. Override via context

Wrap your tree with PluggableComponentRegistry and pass a map of component ids to replacement components. Any usage of Button under that provider will render your custom component instead.

Because pluggable components toString() to their id, you can use the component itself as the key:

import { PluggableComponentRegistry } from "pluggable-react";
import { Button } from "./Button";

const CustomButton = (props: any) => (
  <button className="custom" {...props}>{props.label}</button>
);

function App() {
  return (
    <PluggableComponentRegistry components={{ [Button]: CustomButton }}>
      <Button label="Click me" />
    </PluggableComponentRegistry>
  );
}

You can also use the id string: components={{ "MyApp.Button": CustomButton }}.

Overrides are merged with any parent registry, so you can override only some components at different levels of the tree.

3. Override globally (imperative)

Pluggable components expose a .replace() method so you can set a single global override without context:

import { Button } from "./Button";

Button.replace((props) => <button className="global-override">{props.label}</button>);

// Later: revert to default
Button.replace(null);

Context overrides take precedence over the static override; the static override is used when no context override is provided.

API

| Export | Description | |--------|-------------| | createPluggable(id, DefaultComponent) | Returns a pluggable component with .id, .replace(), displayName, and toString() (returns id, so you can use [Button]: CustomButton). | | PluggableComponentRegistry | Provider that accepts a components map of id → component to override within its subtree. | | usePluggableComponentFromRegistry(idOrComponent) | Hook that returns the override for the given id string or pluggable component from the nearest registry, or undefined. | | PluggableComponentRegistryContext | React context used by the registry (for advanced use). |

Requirements

  • React 18+
  • TypeScript (optional; types are included)

License

MIT