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

@sjlouji/design-system

v0.15.0

Published

A React component library built on Radix UI primitives, Tailwind CSS v4, and shadcn/ui patterns. Ships as an npm package with full TypeScript support.

Readme

@sjlouji/design-system

A React component library built on Radix UI primitives, Tailwind CSS v4, and shadcn/ui patterns. Ships as an npm package with full TypeScript support.

What's in here

100+ production-ready components spanning UI primitives, layout helpers, data display, forms, and AI-specific patterns (streaming text, chat shells, thinking blocks, etc). Every component has Storybook stories and unit tests.

Stack: React 19 · TypeScript 6 · Tailwind CSS v4 · Radix UI · Vite · Storybook 10 · Vitest

Storybook: https://<branch>--6a278cda6ea36483150a66f5.chromatic.com e.g. https://main--6a278cda6ea36483150a66f5.chromatic.com for main


Getting started locally

# Clone and install
git clone [email protected]:sjlouji/design-system.git
cd design-system
npm install

# Start Storybook (component explorer + docs)
npm run storybook

# Start the dev playground (src/main.tsx)
npm run dev

Storybook runs at http://localhost:6006. The dev playground runs at http://localhost:5173.


Available commands

| Command | What it does | |---|---| | npm run dev | Start the Vite dev playground | | npm run storybook | Start Storybook on port 6006 | | npm run build | Typecheck + build the library to dist/ | | npm run build-storybook | Build static Storybook site | | npm run lint | Run ESLint | | npm run typecheck | Run TypeScript without emitting | | npm run test | Run all unit tests (single run) | | npm run test:watch | Run tests in watch mode | | npm run test:coverage | Run tests with v8 coverage report |


Project structure

src/
├── components/          # One folder per component
│   ├── Button/
│   │   ├── Button.tsx       # Component source
│   │   ├── Button.stories.tsx
│   │   ├── Button.test.tsx
│   │   └── index.ts         # Re-export
│   └── ...
├── hooks/               # Shared hooks (use-mobile, etc.)
├── lib/
│   ├── utils.ts         # cn() helper
│   └── test-utils.tsx   # render() wrapper with providers
└── index.ts             # Public package entry point

.github/workflows/
├── ci.yml               # PR validation (lint, typecheck, test, build)
├── release.yml          # main → version bump + GitHub Release + npm publish
└── prerelease.yml       # feature/** → dev prerelease (e.g. 0.1.0-feat-my-thing.42)

scripts/
└── bump-version.mjs     # Conventional commits → semver bump

Using the package

npm install @sjlouji/design-system

Import components and the stylesheet:

// In your app entry
import '@sjlouji/design-system/styles'

// Import components
import { Button, Input, Dialog } from '@sjlouji/design-system'

The package ships both ESM (dist/index.mjs) and CJS (dist/index.cjs) builds.


Contributing

Before you start

  • Node.js 20+ required. Use mise if you have it: mise install.
  • All commits go through lint-staged (ESLint on staged files) and a pre-push test run via Husky.

Adding a new component

  1. Create src/components/MyComponent/ with:
    • MyComponent.tsx — the component
    • MyComponent.stories.tsx — at least a Default story
    • MyComponent.test.tsx — basic render test
    • index.tsexport { MyComponent } from './MyComponent'
  2. Add the export to src/index.ts
  3. Run npm run storybook to verify the story renders correctly
  4. Run npm test to confirm tests pass

Component conventions:

  • Functional components, no class components
  • Use cn() from @/lib/utils for className merging
  • Use data-slot="component-name" on root elements for CSS targeting
  • Named exports only (no default exports)
  • Use CVA (class-variance-authority) for variant-based styling

Story conventions:

  • import type { Meta, StoryObj } from '@storybook/react-vite'
  • Always add args defaults in the meta for required props
  • For components with complex prop types (generics, union-heavy), drop the : Story annotation and let TypeScript infer

Test conventions:

  • import { render } from '@/lib/test-utils' — wraps in TooltipProvider and other global providers
  • Tests live alongside the component, not in a separate __tests__ folder

Commit messages

This repo uses Conventional Commits. The CI release workflow reads these to determine the version bump:

| Prefix | Version bump | |---|---| | feat: | minor (0.x.0) | | fix:, chore:, docs:, etc. | patch (0.0.x) | | feat!: or BREAKING CHANGE in body | major (x.0.0) |

Pull requests

Open PRs against main. The CI workflow runs lint, typecheck, tests, and a full build on every PR. Merging to main automatically triggers a version bump, GitHub Release, and npm publish.

For experimental work, push to a feature/, feat/, fix/, or bugfix/ branch — this triggers a dev prerelease publish tagged with the branch name (e.g. @sjlouji/[email protected]).


Component catalogue

Layout Accordion · AppLayout · AspectRatio · BoardLayout · BreadcrumbGroup · Card · Collapsible · Direction · Drawer · LayoutCol · LayoutRow · Resizable · ScrollArea · Section · Separator · Sheet · Sidebar · SplitLayout · Tabs

Navigation Breadcrumb · Header · Menubar · NavigationMenu · PageHeader · Pagination · Stepper · Timeline · TopNavigation · TreeView

Forms & Inputs AutoSuggest · Calendar · Checkbox · Combobox · DateInput · DatePicker · DateRangeInput · Field · FieldGroup · FileDropzone · FileUpload · Form · Input · InputGroup · InputOTP · Label · NativeSelect · PropertyFilter · RadioGroup · SearchInput · Select · Slider · Switch · Textarea · Toggle · ToggleGroup

Actions Button · ButtonDropdown · ButtonGroup · Command · ContextMenu · CopyButton · DropdownMenu · HoverCard · Popover · Tooltip

Data Display Avatar · AvatarGroup · Badge · Branding · Chart · DataTable · EmptyState · Item · Kbd · Progress · SearchBar · Skeleton · StatCard · StatusBadge · StatusIndicator · Table · Typography

Feedback & Overlays Alert · AlertDialog · Dialog · Flashbar · Sonner · Spinner

AI / Chat ChatInput · ChatMessage · ChatShell · ChatThread · CodeBlock · CodeEditor · ConversationList · MarkdownMessage · MessageActions · MessageFeedback · ModelSelector · PromptCard · PromptInput · PromptLibrary · StreamingText · ThinkingBlock · TokenCounter · TypingIndicator

Utility ActionCard · FileAttachment · Carousel


Versioning & publishing

Versioning is fully automated via GitHub Actions on push to main:

  1. Reads conventional commit messages since the last git tag
  2. Bumps package.json version accordingly
  3. Commits the bump with [skip ci] and pushes a git tag
  4. Creates a GitHub Release with auto-generated notes
  5. Publishes to npm as @sjlouji/design-system with provenance