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

implicit-component

v0.1.1

Published

this is ridiculously simple dependency injection for react components using context and hooks

Downloads

10

Readme

implicit-component

Description

This is ridiculously simple dependency injection for React components using context and hooks.

Install

yarn add implicit-component

or

npm i implicit-component

Usage

Trivial Example

import React from 'react';
import {ComponentContext, useComponentContext} from "implicit-component";

function Header() {
  return <h2>{'Header'}</h2>;
}

function Body() {
  return <p>{'Body'}</p>;
}

const componentList = {Header, Body};

function Page() {
  const {Body, Header} = useComponentContext();

  return (
    <div>
      <Header />
      <Body />
    </div>
  );
}

export default function App() {
  return (
      <ComponentContext list={componentList}>
        <Page />
      </ComponentContext>
  );
}

What does this give us? Absolutely nothing, other than that the components in Page are no longer hard coded. For this app there is absolutely no point in adding more indirection.

Contrived Example

In the next example there are actually a point in the indirection. And a step, al be it a small one, closer to an actual use case.

import React from 'react';
import {ComponentContext, useComponentContext} from "implicit-component";

function Header1() {
  return <h2>{'Header 1'}</h2>;
}

function Header2() {
  return <h2>{'Header 2'}</h2>;
}

function Body1() {
  return <p>{'Body 1'}</p>;
}

function Body2() {
  return <p>{'Body 2'}</p>;
}

function Page() {
  const {Body, Header} = useComponentContext();

  return (
    <div>
      <Header />
      <Body />
    </div>
  );
}

const compList1 = {Header: Header1, Body: Body1};
const compList2 = {Header: Header2, Body: Body2};

export default function App() {
  return (
    <div>
      <ComponentContext list={compList1}>
        <Page />
      </ComponentContext>
      <ComponentContext list={compList2}>
        <Page />
      </ComponentContext>
    </div>
  );
}

Now this was actually useful. We could reuse the Page component and render different components based only on the component context.

Nested Contexts

Contexts are nested by prototype chaining. That means we can create a global list of components that we can override locally by nesting contexts, and the none overridden components in the parent contexts are still accessible.

import React from 'react';
import {ComponentContext, useComponentContext} from "implicit-component";

function Header1() {
  return <h2>{'Header 1'}</h2>;
}

function Body1() {
  return <p>{'Body 1'}</p>;
}

function Body2() {
  return <p>{'Body 2'}</p>;
}

function Page() {
  const {Body, Header} = useComponentContext();

  return (
    <div>
      <Header />
      <Body />
    </div>
  );
}

const compList1 = {Header: Header1, Body: Body1};
const compList2 = {Body: Body2};

export default function App() {
  return (
    <ComponentContext list={compList1}>
      <ComponentContext list={compList2}>
        <Page />
      </ComponentContext>
    </ComponentContext>
  );
}

Here we override the body in the inner context butt are still using header1.