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

@cocajs/atomic-react

v1.0.0

Published

Achieve atomic and decoupled component design for truly reusable React components. Write once, compose anywhere.

Downloads

13

Readme

Atomic React

Write once, compose anywhere. True component reusability through atomic design.

The Problem

React lacks built-in support for type-safe dependency injection and factory patterns. This forces developers into prop drilling, context complexity, or tightly coupled components where UI, state, and business logic become entangled. The result: "Whack-A-Mole" states where one change breaks another feature.

Why Atomic?

Atomic React solves this through type-safe dependency injection and factory patterns for React components:

  • Type-Safe DI - Inject state and business logic with full TypeScript support
  • Factory Pattern - Create reusable component factories with isolated dependencies
  • Zero Coupling - UI, state, and business logic completely separated
  • No Prop Drilling - Dependencies injected directly into components

How It Works

Factory pattern with dependency injection across three layers:

  1. UI - Pure components receive dependencies as props
  2. State - Independent Zustand stores injected into each "atom"; all other atoms can access the Zustand stores
  3. Business - Functions and services injected

Installation

npm install atomic-react zustand

Examples

atomic({ state, stateActions, functions, component })

interface SearchState {
  searchTerm: string;
}

interface SearchActions {
  setSearchTerm: (term: string) => void;
  clear: () => void;
}

interface SearchFunctions {
  validateSearchTerm: (term: string) => boolean;
  formatSearchTerm: (term: string) => string;
}

const searchFunctions: SearchFunctions = {
  validateSearchTerm: (term: string) => term.length > 0,
  formatSearchTerm: (term: string) => term.trim(),
};

export type SearchComponentProps = {
  searchTerm: string;
  setSearchTerm: (searchTerm: string) => void;
  validateSearchTerm: (searchTerm: string) => boolean;
  formatSearchTerm: (searchTerm: string) => string;
};

export function SearchComponent({
  searchTerm,
  setSearchTerm,
  validateSearchTerm,
  formatSearchTerm,
}: SearchComponentProps) {
  useEffect(() => {
    if (searchTerm && validateSearchTerm(searchTerm)) {
      console.log('searchTerm', searchTerm);
    }
  }, [searchTerm, validateSearchTerm]);

  const handleChange = (e: React.ChangeEvent<HTMLInputElement>) => {
    const formatted = formatSearchTerm(e.target.value);
    setSearchTerm(formatted);
  };

  return (
    <div>
      <input
        value={searchTerm}
        onChange={handleChange}
        placeholder="Search..."
      />
    </div>
  );
}

const SearchAtom = atomic<SearchState, SearchFunctions, SearchActions>({
  state: {
    searchTerm: '',
  },
  stateActions: (set, _, functions) => ({
    setSearchTerm: (term: string) => {
      if (functions.validateSearchTerm(term)) {
        set({ searchTerm: term });
      }
    },
    clear: () => {
      set({ searchTerm: '' });
    },
  }),
  functions: searchFunctions,
  component: SearchComponent,
});

Returns: { useStore, Atomic, select }

createSelector(useStore, selector)

const useSearchTerm = createSelector(
  SearchAtom.useStore,
  (state) => state.searchTerm,
);

SearchAtom.select(selector)

const useSearchTerm = SearchAtom.select((state) => state.searchTerm);

License

MIT © Manuel Coca