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

nojsui

v1.0.0

Published

Copy NojsUI components into your project (shadcn-style). The only JS artifact in NojsUI, and it is optional.

Readme

nojsui

The CLI for NojsUI. It copies component source into your project shadcn-style — you own the files afterwards.

This is the only JavaScript NojsUI ships, and it is entirely optional: the components are plain .css and .html files you can also copy by hand from @nojsui/core.

Usage

npx nojsui list            # what the kit has
npx nojsui add popover     # copy popover into ./nojsui/

add writes:

nojsui/
  tokens.css          only if it is not already there
  base.css            only if it is not already there
  popover/
    popover.css
    popover.html

Then link the three stylesheets in that order and paste the markup. You own the files from that point on — there is no config file, no lockstep and nothing to migrate.

Options

| Option | Default | What it does | | --- | --- | --- | | --dir <path> | nojsui | Where to write, relative to where you run it. | | --force | off | Overwrite existing component files. Without it, an add that would overwrite anything writes nothing and exits 1. | | -h, --help | | Usage. | | -v, --version | | The version, which is also the @nojsui/core version it copies from. |

tokens.css and base.css are never overwritten, with or without --force — they are yours to edit, and a second add must not undo that.

Where the files come from

The CLI copies from @nojsui/core, its single dependency, pinned to the exact version the CLI ships with. Nothing is fetched at runtime, so nojsui add works offline and always installs the components that were tested with that release. See ADR 0025.

Links

  • Docs and live demos: https://nojsui.com

MIT © SekiUI