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

@marom31/qwiik-design-system

v0.1.0

Published

Qwiik Design System - Enterprise B2B SaaS logistics React component library

Readme

Qwiik Design System

Token-driven UI library for Qwiik's B2B logistics products. The repository currently focuses on establishing a reliable design token pipeline and iterating on the first wave of component prototypes.

Project status

  • ✅ Design tokens compile to CSS variables, JS, Tailwind, and TypeScript via pnpm build:tokens
  • ✅ Storybook runs locally with prototype components that consume the token set
  • ✅ Generated stylesheet bundle (dist/styles.css) is now available for distribution
  • ✅ Package entry point exports core components and utilities for consumption
  • 🚧 Automated tests beyond the cn helper have not been authored yet

Documentation

Comprehensive guides and references are available in the docs/ directory:

Setup & Verification

Design System Guidelines

Development Guides

Project History

Installation

npm install @qwiik/design-system
# or
pnpm add @qwiik/design-system
# or
yarn add @qwiik/design-system

Usage

Option 1: With Pre-built Styles (Recommended)

Import the pre-built CSS bundle for instant use without Tailwind configuration:

// Import the stylesheet
import '@qwiik/design-system/dist/styles.css';

// Import components
import { Button, Input, Card } from '@qwiik/design-system';

function App() {
  return (
    <Button tone="brand" level="primary">
      Click me
    </Button>
  );
}

Option 2: With Tailwind Configuration (Advanced)

For advanced customization, configure Tailwind in your project to process the design system:

// tailwind.config.js
module.exports = {
  content: [
    './src/**/*.{js,ts,jsx,tsx}',
    './node_modules/@qwiik/design-system/**/*.{js,ts,jsx,tsx}',
  ],
  // ... your config
};

Working locally

Prerequisites

  • Node.js ≥ 18
  • pnpm ≥ 9

Setup

# Install dependencies
pnpm install

# Start Storybook for component development
pnpm dev

# Regenerate tokens after editing files in design-tokens/ or components.json
pnpm build:tokens

Available scripts

  • pnpm dev – Launch Storybook at http://localhost:6006
  • pnpm build:tokens – Run the Style Dictionary pipeline and refresh generated artifacts
  • pnpm build – Transform tokens, bundle JavaScript with tsup, and generate CSS bundle (dist/styles.css)
  • pnpm lint – ESLint over src
  • pnpm type-check – Run tsc --noEmit
  • pnpm test / pnpm test:coverage – Vitest test runner (currently minimal coverage)
  • pnpm test:e2e – Playwright suite scaffold

Token workflow

  1. Update raw tokens in design-tokens/ or components.json
  2. Execute pnpm build:tokens
  3. Consume the generated outputs:
    • src/tokens/variables.css
    • src/tokens/tokens.js
    • src/tokens/tailwind-tokens.js
    • src/tokens/types.d.ts
    • tailwind.config.ts

Next steps

  • Publish the core primitives from src/components once their APIs settle
  • Expand automated tests to cover critical components and token usage scenarios
  • Add comprehensive component documentation and examples

Contributing

We welcome contributions! Please see our Contributing Guide for details on:

  • Development workflow
  • Code quality standards
  • Commit conventions
  • Pull request process

License

MIT © Qwiik - See LICENSE for details.