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

@eevenkoto/react

v0.9.5

Published

Eevenkoto React component wrappers

Readme

@eevenkoto/react

Thin React wrappers around Eevenkoto’s BEM classes. Source lives under core/ and domain/ (Atoms / Molecules / Organisms); the package barrel keeps a stable public API. Styling comes from @eevenkoto/css; class assembly from @eevenkoto/core.

Install

npm install @eevenkoto/css @eevenkoto/react react

Peer: react ^18 or ^19.

Usage

import '@eevenkoto/css/styles.css';
import '@eevenkoto/css/button.css';
import '@eevenkoto/css/flow.css';
import '@eevenkoto/css/prose.css';
import '@eevenkoto/css/heading.css';
import '@eevenkoto/css/paragraph.css';
import { Button, Flow, Heading, Paragraph, Prose } from '@eevenkoto/react';

export function Example() {
  return (
    <Flow>
      <Heading level={2} text="Section title" />
      <Paragraph text="Body copy." />
      <Button variant="primary" label="Save" />
    </Flow>
  );
}

@eevenkoto/css is an optional peer — import each component sheet (for example @eevenkoto/css/badge.css) or the UI is unstyled. Live Storybook docs under Framework packages show HTML, React, and Vue for every published component.

Core

  • Atoms: Avatar, Badge, Button, Caption, Chip, Frame, Heading, Icon, InlineRef, Input, LinkButton, ListItem, Paragraph, Popover, Property, Scroll, Stat, StatusDot, TableCell
  • Molecules: Card, Catalog, CatalogTile, Field, Flow, List, Menu, Notice, Prose, PropertyList, SegmentedControl, Table, TooltipCard
  • Organisms: TableShell

Button = in-page action. LinkButton = prominent URL CTA (href required; import @eevenkoto/css/link-button.css). Never put href on Button. Inline terms use InlineRef.

Domain

  • Atoms: EntityRef
  • Molecules: AbilityScore, StatblockFeature, StatblockSection
  • Organisms: AbilityScoreGroup, Statblock, Spellblock

Flow / Prose / Frame / Scroll / TableShell use children (not a content string like @eevenkoto/html). For bare-tag reading content, compose both hosts: <Prose className="eevenkoto-flow">…</Prose>.

Related

  • @eevenkoto/css — styles (required for appearance; consume / never rules live there)
  • @eevenkoto/html — reference vanilla renderers
  • @eevenkoto/vue — Vue equivalents

For agents: feed Storybook /llms.txt or /llms-full.txt (generated via npm run generate:llms).