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

@thewanionly327/ui

v3.0.0

Published

This package contains shared UI components for use across the MedusaJS Dummy Store monorepo. It is designed to provide a consistent design system and reusable building blocks for your applications.

Readme

UI Package

This package contains shared UI components for use across the MedusaJS Dummy Store monorepo. It is designed to provide a consistent design system and reusable building blocks for your applications.

Purpose

  • Centralize UI components for reuse in multiple apps (storefront, admin, etc.)
  • Promote consistency and maintainability
  • Enable rapid development by sharing common UI patterns

Adding Components from gfed-registry

You can easily add new components from the gfed-registry using the following command:

pnpm dlx shadcn@latest add https://gfed-registry.vercel.app/r/breadcrumbs.json

Replace the URL with the component you want to add. This will automatically fetch and integrate the component into the UI package.

Steps:

  1. Browse gfed-registry for available components.
  2. Copy the component link (e.g., /r/breadcrumbs.json).
  3. Run the command above in the root of the UI package.
  4. The component will be added to src/components and ready for use.

Usage

Import components from this package in your apps:

import { Breadcrumbs } from '@thewanionly327/ui/components/breadcrumbs/breadcrumbs';

Folder Structure

The most important part of the UI package is the src folder, which contains all the code you need to work with:

src/
├── components/
│   ├── [base components]        # Single .tsx files from shadcn
│   └── [custom/grouped components] # Folders for components from gfed-registry or custom components
├── hooks/                       # Custom React hooks
├── lib/                         # Utility functions and helpers
└── styles/                      # Global CSS and style files
  • Base components: Single .tsx files in components/ (added via shadcn)
  • gfed-registry/custom components: Folders in components/ for components from gfed-registry or custom project-specific UI elements
  • hooks: For custom React hooks
  • lib: Utility functions and helpers
  • styles: Global CSS and style files

This structure keeps the UI code organized and easy to find.

Contributing

Feel free to add your own components or update existing ones. For custom additions, place your components in src/components and export them as needed.


For more details, see the documentation in each component folder or reach out to the team.