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

@designa8/vibedesign-wise

v0.5.1

Published

Design system "wise" generated by atom-server.

Readme

@designa8/vibedesign-wise

Generated design system, version 0.5.1.

Local install (npm link)

From this directory:

npm link

Then, in the consumer app:

npm link @designa8/vibedesign-wise

Imports

import { /* atoms */ } from "@designa8/vibedesign-wise";

The CSS (design tokens, Tailwind utilities, and the design system font loaded from Google Fonts) is bundled into the package entry point and injected automatically by your bundler — no separate CSS import needed.

Vite configuration (local npm link only)

When using npm link, the package fonts live outside your project root and Vite's dev server will block them by default. Add server.fs.allow to your vite.config.js / vite.config.ts:

export default defineConfig({
  server: {
    fs: {
      allow: ['..', '/path/to/.published-packages'],
    },
  },
})

Replace /path/to/.published-packages with the absolute path printed by npm link (the directory that contains this package folder). This step is not needed when the package is installed from a real registry.

Global CSS compatibility

The package's utility classes (spacing, colours, border-radius, etc.) are compiled as unlayered CSS rules. They therefore beat standard resets such as * { margin: 0; padding: 0; box-sizing: border-box } by normal specificity (class selector 0-1-0 > universal selector 0-0-0). No special setup is needed for a typical Vite / Create-React-App / Next.js project.

The one exception is the body font. The design system injects body { font-family: var(--font-body) } inside @layer base, which any unlayered body { font-family: ... } rule in your own CSS will override. Remove that override, or replace it with the design system variable:

body {
  font-family: var(--font-body); /* use the design system's configured font */
}