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

@prithvirajsinh-jadav/ui

v0.0.11

Published

UI primitives (shadcn-style) and opinionated wrappers

Vulnerabilities

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

Links

Maintainers

prithvirajsinh-jadavprithvirajsinh-jadav

Keywords

Readme

@prithvirajsinh-jadav/ui

Primitives (./ui/*) and core wrappers (./core/*) for apps that use Tailwind v4 + shadcn-style tokens.

The npm scope matches your npm username so you can publish without creating an organization. To use a different scope (e.g. @silly-labs), create that org on npmjs.com first, then change the "name" in package.json.

Install

npm i @prithvirajsinh-jadav/ui

Peers: react, react-dom, next (for next/link / next/image in a few components), next-themes, tailwindcss v4, tw-animate-css, shadcn (styles entry below).

Styles (no manual @source)

The package ships styles.css (Tailwind v4, token theme, and internal @source for components). You can load it in two ways (pick one pattern per app; the bundler usually dedupes the same file).

A — import any root export (adds a side effect on dist/index.js that loads styles.css):

import { Button, ThemeProvider, cn } from "@prithvirajsinh-jadav/ui"

B — CSS only in your global stylesheet (no JS from the package yet):

@import "@prithvirajsinh-jadav/ui/styles.css";

Next.js App Router — root layout (recommended if you do not want the root barrel in a server layout):

import "@prithvirajsinh-jadav/ui/styles.css"

Place it alongside import "./globals.css" so tokens and Tailwind run before your app CSS.

You do not need per-app @source paths into this package’s src/.

styles.css defines --font-sans, --font-mono, and --font-heading on :root (system stacks). Optional: override --font-sans / --font-mono on <html> with next/font (variable: '--font-sans'), same as any Tailwind app.

Imports

Recommended: opinionated wrappers + shared helpers from the package root (single import path):

import { Button, AppCard, cn, ThemeProvider } from "@prithvirajsinh-jadav/ui"

Primitives only (low-level components/ui, e.g. different Button API than core): subpath @prithvirajsinh-jadav/ui/ui/<name>.

Deep core/* subpaths still exist for bundlers that need granular chunks; prefer root imports for app code.