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

@nextide/ui

v2.3.1

Published

Shared Nextide React components and product interface patterns.

Readme

@nextide/ui

Shared Nextide React components and product interface patterns, built with shadcn/ui, Base UI, Tailwind CSS 4, and React 19.

Install

Pin an exact release so upgrades remain deliberate:

pnpm add --save-exact @nextide/[email protected]
pnpm add --save-dev --save-exact [email protected] @tailwindcss/[email protected]

The consumer must provide React 19, React DOM 19, and Tailwind CSS 4. In a Vite app, enable Tailwind's Vite plugin:

// vite.config.ts
import tailwindcss from "@tailwindcss/vite"
import react from "@vitejs/plugin-react"
import { defineConfig } from "vite"

export default defineConfig({ plugins: [react(), tailwindcss()] })

Import the shared stylesheet once in the application entry point, before any app-specific styles:

import "@nextide/ui/globals.css"
import "./app.css"

Products that need the optional Obviously display face may import it separately:

import "@nextide/ui/display-font.css"

This enables font-display for rare, single-line hero and report masthead text. Do not apply it to controls, navigation labels, forms, tables, metrics, or body copy. Without the optional import, font-display falls back to the standard UI stack.

Use

Import through explicit public package exports:

import { AppShell } from "@nextide/ui/blocks/app-shell"
import { Button } from "@nextide/ui/components/button"
import { PopoverTrigger } from "@nextide/ui/components/popover"
import { useStagedDrawer } from "@nextide/ui/hooks/use-staged-drawer"

The primitives use Base UI. Compose trigger controls with Base UI's render prop rather than Radix's asChild convention:

function DetailsTrigger() {
  return (
    <PopoverTrigger render={<Button variant="outline" />}>
      Open details
    </PopoverTrigger>
  )
}

Do not import internal src or dist paths. The supported exports are globals.css, components/*, blocks/*, hooks/*, and lib/*.

v2 foundation

Version 2 uses a metric-stable platform UI stack, a fixed type scale, tonal surfaces, and signal color reserved for current action and state. Use the Tailwind utilities text-ui-brand, text-ui-display, text-ui-headline, text-ui-title, text-ui-body, text-ui-label, text-ui-caption, and text-ui-micro; everyday product UI uses only 400 and 500 weights. Brand and Display are the sole 700 exceptions.

The default stylesheet no longer loads Obviously or another bundled UI font. The separate display stylesheet ships one explicit Obviously weight for hero use; controls, navigation labels, forms, tables, metrics, and body copy must not depend on it or on per-component baseline offsets.

Named surface radii resolve to 8, 10, or 12 pixels. True circles and data marks are the only rounder exceptions. Shared motion uses 120, 160, 220, and 300 millisecond tokens for instant, control, state, and layout changes.

This package is publicly downloadable but proprietary. No license to copy, modify, or redistribute it is granted.