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

@lexicon_design/react

v0.1.1

Published

lexicon design system — React components, design tokens, a Tailwind preset, and a branded CLI.

Readme

@lexicon_design/react

The lexicon design system as React components. Early release (0.1.0).

Install

npm i @lexicon_design/react react react-dom

Use — drop-in CSS (simplest)

Import the precompiled stylesheet once, wrap your app in LexiconProvider, and use components:

import '@lexicon_design/react/styles.css';
import { LexiconProvider, Button, Dialog } from '@lexicon_design/react';

export function App() {
  return (
    <LexiconProvider theme="dark">
      <Button variant="primary">Save</Button>
    </LexiconProvider>
  );
}

LexiconProvider renders the .lexicon-root scope that the design tokens and portaled overlays depend on. styles.css ships the token variables, the component utility classes, and the --tw-* initializers — but no CSS reset, so it won't clobber your global styles.

Use — Tailwind preset (if you already use Tailwind)

// tailwind.config.js
module.exports = {
  presets: [require('@lexicon_design/react/tailwind-preset')],
  content: [
    './src/**/*.{ts,tsx}',
    './node_modules/@lexicon_design/react/**/*.js',
  ],
};
import '@lexicon_design/react/tokens.css'; // token variable definitions
import { LexiconProvider, Button } from '@lexicon_design/react';

The preset maps lexicon's token scale (colors, type, spacing, radius, motion, z-index) onto Tailwind's theme; tokens.css provides the CSS variables the preset's utilities reference. Your own @tailwind base supplies the --tw-* initializers in this mode.

CLI

The package ships a branded command line. Run it without installing anything extra:

npx @lexicon_design/react

That first run shows the lexicon wordmark, your installed version, activation status, and license state. Commands:

| command | what it does | | --- | --- | | lexicon | welcome screen, or your status dashboard once activated | | lexicon activate [key] | unlock lexicon with the license key from your purchase portal | | lexicon doctor | full diagnostic: environment, project wiring, connection, token conformance | | lexicon pull [asset] | list or download premium assets (figma library, templates, recipes) | | lexicon outdated | show available updates for pulled assets | | lexicon figma | open your figma access in the browser | | lexicon help | command reference |

doctor checks your node version, react/typescript/tailwind wiring, styles.css/tokens.css imports, LexiconProvider, git state, and connection latency — then scans your repo's source with the lexicon conformance rules (hardcoded colours, off-token values). Every warning carries a fix-it hint. Use --json in CI: exit code 0 means no failures.

Flags: --json · --verbose · --no-color. The CLI honours NO_COLOR and degrades to plain output on non-TTY streams, so logs and CI stay readable. License keys are stored at ~/.config/lexicon/credentials.json (mode 600) and re-verified quietly at most once a week — going offline never locks you out.

Notes

  • Scope: React only at 0.1.0.
  • Fonts: components reference --font-sans / --font-mono with system fallbacks. Install the matching @fontsource families if you want the exact lexicon typefaces.
  • Tree-shaking: components are emitted as per-module ESM, so unused components drop out of your bundle.