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

@dcaldeira/design-system

v1.0.1

Published

A minimal React starter for small projects, combining a lightweight design system with a reusable component library.

Vulnerabilities

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

Links

Maintainers

dcaldeiradcaldeira

Keywords

Readme

Baseline

A minimal React starter for small projects, combining a lightweight design system with a reusable component library.

Tech Stack

  • Framework — Next.js 14 (App Router)
  • Language — TypeScript (strict mode)
  • Styling — SCSS Modules
  • Testing — Vitest + Testing Library
  • Linting — ESLint (next/core-web-vitals)
  • Formatting — Prettier with @trivago/prettier-plugin-sort-imports
  • Package Manager — pnpm

Getting Started

pnpm install
pnpm dev

Open http://localhost:3000 to see the app.

Scripts

| Command | Description | | ----------------- | ------------------------ | | pnpm dev | Start development server | | pnpm build | Build for production | | pnpm start | Start production server | | pnpm lint | Run ESLint | | pnpm format | Run Prettier | | pnpm test | Run unit tests once | | pnpm test:watch | Run tests in watch mode |

Project Structure

src/
  app/              # Next.js App Router pages & layouts
  components/
    ui/             # Reusable UI components (button, input, select, stepper)
    layout/         # Layout primitives (container, stack)
  hooks/            # Shared custom hooks
  styles/
    tokens/         # Design tokens (colors, spacing, typography, radius, shadows)
    theme/          # Light & dark CSS custom properties
    reset.scss      # Minimal browser reset
    globals.scss    # Global styles entry point
  types/            # Shared TypeScript types
  utils/            # Pure utility functions
  index.ts          # Public barrel export

Component Conventions

Each component lives in its own folder:

ComponentName/
  ComponentName.tsx          # Component implementation
  ComponentName.module.scss  # SCSS module styles
  ComponentName.test.tsx     # Unit tests
  index.ts                   # Barrel export

Props are typed inline or in a dedicated types.ts file.
Use the cn() utility from @/utils/cn for conditional class merging.

Styling

SCSS modules are used exclusively — no CSS-in-JS or inline styles.

Design tokens are organised under src/styles/tokens/ as SCSS variables and are consumed via @use. Theme values are exposed as CSS custom properties and toggled via a data-theme attribute.

To apply a theme:

<html data-theme="dark"></html>

Path Aliases

@/* maps to ./src/* in both TypeScript and Vitest.