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

@textui/cli

v0.5.0

Published

TextUI developer CLI - init, add, create, doctor - and primitives for building your own

Readme

@textui/cli

npm license

textui - set a project up, copy components into it, and find out what the terminal in front of you can actually do.

npx @textui/cli init

Components are copied, not imported

@textui/widgets is a dependency you install. The registry behind textui add is the opposite: it writes the source into your project and you own it from there, edits included.

textui add service-table     # writes src/ui/service-table.tsx
textui create dashboard      # writes a whole screen
textui diff                  # what you have edited since it was copied

diff matters because owning the source means upstream fixes do not reach you. It tells you which files have drifted, so an update is a decision rather than a surprise.

Commands

| | | |---|---| | init | Set up TextUI in this project | | add | Copy components into your project | | create | Scaffold a template into your project | | list | Registry components, templates and themes | | theme | List themes, or preview one | | registry | Manage component registries | | diff | Which copied components have drifted from upstream | | doctor | What this terminal can do, and what the project looks like |

doctor is the one to run first when something renders wrong: it reports the unicode level, colour depth, mouse and keyboard protocol actually detected, which is usually the answer.

Building your own

createCli() is exported, and @textui/cli/app is the primitives under it - commands, options, help and prompts. Deliberately small: the point is that an application built on TextUI can combine plain commands with interactive screens without a second framework and a second idea of what an argument is.

Runtime

Depends on @textui/core and @textui/terminal. Uses node:fs, node:path and node:crypto - it is the one library package here that touches a disk. Node 22+ and Bun.

Documentation

https://softov.github.io/textui/


Part of TextUI - documentation - getting started

@textui/kit one install · @textui/core the runtime · @textui/widgets the catalog · @textui/terminal adapters and input · @textui/testing the harness · @textui/cli the CLI