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

ember-design-system

v0.2.4

Published

A tight, opinionated design system — warm neutrals, ember accent, dual-mode.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

mediocre1337mediocre1337

Keywords

Readme

Ember — Design System

A tight, opinionated design system for personal brand and product UI — warm neutrals, ember accent, dual-mode (light + dark, equal priority).

"Function before flourish. Craft is visible in restraint. Warm, not sterile. One weird thing. Both modes are first-class. Respect the medium." — design-brief.md

Links

  • Showcase site — https://ember-design-system.vercel.app
  • Storybook — https://ember-storybook.vercel.app
  • Source brief — design-brief.md

Stack

  • React 19 + TypeScript + Vite
  • CSS Modules + CSS custom properties (mode-aware tokens)
  • Storybook 10 (@storybook/react-vite)
  • Lucide icons (1.5px stroke, outline only)
  • react-router-dom for showcase routing

What is in the box

Tokens — color, type scale, spacing, radius, motion, elevation. All mode-aware via [data-theme="light" | "dark"] on <html>.

Components — 60+ total, covering the full shadcn/ui surface, rebuilt from scratch on Ember tokens (CSS Modules, no Radix/Tailwind, no heavy runtime deps):

  • Layout: Box, Flex, Stack, Inline, Grid, Aspect Ratio.
  • Primitives: Text, Overline, Dot, Mark, Image, Button, IconButton, Input, Textarea, Select, Checkbox, Radio, Switch, Label, Badge, Tag, Avatar, Divider, Tooltip, Spinner, Kbd, Popover, Skeleton, Progress, Toggle, Toggle Group, Slider, Input OTP, Scroll Area.
  • Patterns: Card, Modal (Dialog), Alert, Alert Dialog, Drawer (Sheet), Toast, Tabs, Accordion, Collapsible, Navigation (top + side), Breadcrumb, Pagination, Table, Empty State, Form Field, Hover Card, Dropdown Menu, Context Menu, Menubar, Command, Combobox, Calendar, Date Picker, Carousel, Resizable.
  • Editorial: Article Header, Pull Quote, Margin Note, Code Block, Inline Code, Footnote, Author Byline, Tag Cloud, Reading Progress.

Every interactive component ships full keyboard support, ARIA roles, focus management, controlled/uncontrolled state, dual-mode tokens, and unit tests. Floating components (Popover, menus, hover card, combobox, date picker) share one in-house positioning engine (useFloating) — no @floating-ui or other external dependency.

Note on Chart: shadcn's Chart is a thin Recharts wrapper. It's intentionally omitted — pulling a heavy charting dependency would break this system's "from scratch, no heavy deps" stance. Wire your charting lib of choice into an Ember Card instead.

Develop

npm install
npm run dev          # showcase app  -> http://localhost:5173
npm run storybook    # Storybook     -> http://localhost:6006

Build

npm run build              # outputs to dist/
npm run build-storybook    # outputs to storybook-static/

Project layout

src/
  styles/                 tokens.css, base.css, typography.css
  lib/
    components/
      primitives/         15 atomic components
      patterns/           12 composite components
      editorial/          9 long-form components
    hooks/                useTheme
    utils/                cn
  pages/                  Home, Foundations, Components, Editorial, About
  showcase/               AppShell (nav, theme toggle, signature footer)
.storybook/               main.ts, preview.ts, fonts.css

Each component lives in its own folder with Name.tsx, Name.module.css, Name.stories.tsx, and index.ts.

The "one weird thing" clause

The system permits exactly one element per surface that breaks the grid intentionally. On this showcase site: a hand-drawn signature in the footer, in the ember accent. It is the anti-template clause — it prevents the system from collapsing into "tasteful dev portfolio #4,892."

License

MIT.