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

@yarcl/react

v0.5.0

Published

Yet another react component library. Your config file is the design system: every key becomes a typed prop and a rendered style.

Readme

@yarcl/react

Yet another react component library. Your config file is the design system: every key becomes a typed prop and a rendered style.

From an existing React project using Vite, webpack, Rspack, Rollup or esbuild, run:

npx @yarcl/react init

This installs the package, adds the detected build plugin and TypeScript path mapping, and creates src/yarcl.config.ts. The equivalent commands are pnpm dlx @yarcl/react init, yarn dlx @yarcl/react init and bunx @yarcl/react init.

For manual setup:

npm install @yarcl/react
// vite.config.ts
import react from '@vitejs/plugin-react';
import { defineConfig } from 'vite';
import yarcl from '@yarcl/react/vite';

export default defineConfig({ plugins: [react(), yarcl({ config: 'src/yarcl.config.ts' })] });

For webpack, Rspack, Rollup or esbuild, import the plugin from the matching @yarcl/react/<build-tool> entry point.

Every build plugin also emits yarcl.tokens.css in the build output directory for server templates and other pages outside the React app. It contains only CSS variables and color-scheme, without component styles or font loading. Set emitTokens: false or emitTokens: '' to disable it, or pass a filename such as emitTokens: 'styles/tokens.css' to customize its output-relative path.

// tsconfig.json
{
  "compilerOptions": {
    "paths": {
      "@yarcl/config": ["./src/yarcl.config.ts", "./node_modules/@yarcl/react/dist/yarcl.config.d.ts"]
    }
  }
}
// src/yarcl.config.ts
import { defineConfig } from '@yarcl/react/define';
import defaults from '@yarcl/react/defaults';

export default defineConfig({
  ...defaults,
  colors: {
    ...defaults.colors,
    brand: { light: '#4f46e5', dark: '#a5b4fc' },
  },
});
import { Button } from '@yarcl/react';

<Button color="brand">Save</Button>;

Documentation: yarcl.dev

For coding agents working in an installed project, read node_modules/@yarcl/react/llms.txt. The package copies this guide from the docs site during its build, so it matches the installed version. The package also includes a short AGENTS.md pointer for agents that inspect dependency directories.

License

MIT