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

@jem-open/jem-ui

v0.4.0

Published

JEM Design System - React component library with Tailwind CSS

Readme

@jem-open/jem-ui

License

JEM Design System - A React component library with Tailwind CSS design tokens, built with Radix UI primitives and Class Variance Authority.

Installation

npm install @jem-open/jem-ui

Peer Dependencies

The following peer dependencies are required:

npm install react@"^18.0.0 || ^19.0.0" react-dom@"^18.0.0 || ^19.0.0" tailwindcss@"^3.4.0"

All other dependencies (Radix UI components, Lucide icons, etc.) are bundled with the package, so you don't need to install them separately.

Integration

1. Import the CSS Variables

In your app's root or layout file:

import "@jem-open/jem-ui/styles.css"

This CSS file defines the design tokens (colors, spacing, etc.) as CSS variables.

2. Configure Tailwind

Update your tailwind.config.js to use the JEM preset:

const jemPreset = require("@jem-open/jem-ui/tailwind-preset");

module.exports = {
  presets: [jemPreset],
  content: [
    "./src/**/*.{ts,tsx}",
    // IMPORTANT: Include jem-ui dist files so Tailwind scans them
    "./node_modules/@jem-open/jem-ui/dist/**/*.{js,mjs}",
  ],
  // your other config...
};

Why both steps are needed:

  • The CSS variables (styles.css) provide the actual color values referenced by the preset
  • The Tailwind preset extends Tailwind with JEM design tokens (colors, spacing, etc.)
  • The content path ensures Tailwind scans the library's components for class names

Example

import { Button } from "@jem-open/jem-ui"

export default function App() {
  return (
    <Button variant="primary" size="lg">
      Click me
    </Button>
  )
}

Contributing

We welcome contributions! Please see CONTRIBUTING.md for guidelines.

Local Development

Once you have cloned the repository:

  1. Install dependencies:
npm install
  1. Start Storybook for component development:
npm run storybook

Storybook will open at http://localhost:6006 where you can view and interact with all components.

Making Changes

  1. Create a feature branch from main:
git checkout -b feature/your-feature-name
  1. Make your changes following the existing patterns in components/ and stories/

  2. Test your changes in Storybook and ensure lint passes:

npm run lint
  1. Commit and push your changes:
git add .
git commit -m "Description of your changes"
git push origin feature/your-feature-name
  1. Open a Pull Request against the main branch

Quality checks (linting, type checking) will run automatically on your PR.

Publishing

After your PR is approved and merged to main, create a release to publish the changes:

  1. Navigate to https://github.com/Jem-Open/jem-ui/releases/new
  2. Create a new tag (e.g., v0.2.1) and click "Create new tag on publish"
  3. Click "Generate release notes" for an automatic changelog
  4. Review and publish the release

The GitHub Actions workflow will automatically build and publish to npm.

License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.