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

@useloops/design-system

v1.4.737

Published

The official React based Loops design system

Readme

@useloops/design-system

The React + TypeScript design system for the Loops platform and marketing website. Built on MUI v9 + Emotion, documented in Storybook, and published as a tree-shakeable npm library.

Architecture decisions and their rationale live in docs/adr/README.md.

Commands

bun install          # install deps (use bun, never npm/npx)
bun run dev          # Storybook dev server on :6006 (primary dev loop)
bun run component    # scaffold a new component (hygen)
bun run icons        # regenerate icons from Figma (setup below)
bun test             # run unit tests
bun run tsc          # typecheck (tsc --noEmit)
bun run package      # build the npm library (Rollup, CJS + ESM + .d.ts)
bun run build        # build the static Storybook site

Synchronising icons with Figma

  • Create a personal access token in Figma: Settings → Security → Personal access tokens
  • Create an .env file at scripts/useloops-icon-generator/.env
  • Install packages: cd scripts/useloops-icon-generator && bun install
  • Run bun run icons from the root dir
  • Check the Brand Core/Icons story in Storybook to verify the expected icons updated

Storybook

Run bun run dev (port 6006). We're on Storybook 10 (@storybook/react-vite).

Controls are defined explicitly per story — TypeScript docgen is disabled, so each story declares its own argTypes/args (no auto-inferred controls). See ADR-0001 for the rationale and how to re-enable inference.

Importing

Three import styles are supported (see ADR-0002 for the why):

// 1. Barrel — imports from the root
import { Button, Avatar, Text } from '@useloops/design-system';

// 2. System-level
import { Button, Avatar, Text } from '@useloops/design-system/WebCore';
import { Navigation, Header, KpiIndicator } from '@useloops/design-system/Platform';
import { Icon } from '@useloops/design-system/BrandCore';
import { PlanTierCard, TickGroup } from '@useloops/design-system/Marketing';
import { ThemeProvider, useTheme } from '@useloops/design-system/theme';
import { omitProps, pluralise, useBreakpoint } from '@useloops/design-system/utils';

// 3. Individual component — best for tree-shaking
import Button from '@useloops/design-system/WebCore/Button';
import Navigation from '@useloops/design-system/Platform/Navigation';
import Icon from '@useloops/design-system/BrandCore/Icon';

Type definitions ship with every import style:

import Button, { ButtonProps } from '@useloops/design-system/WebCore/Button';

Available systems

  • BrandCore — brand-specific components (Icon)
  • Marketing — marketing page components (PlanTierCard, TickGroup, PlanFeatureTable)
  • Platform — platform-specific components (Navigation, Header, KpiIndicator, …)
  • WebCore — core web components (Button, Avatar, TextField, Text, …)
  • theme — theme configuration and provider
  • utils — utility functions and hooks