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

create-ultimate

v18.0.0

Published

bunx create-ultimate myapp — scaffold an Ultimate monorepo

Readme

create-ultimate

bunx create-ultimate myapp && cd myapp && bin/setup && x dev

bin/setup is the scaffold's own script and it is not optional: x new writes files and installs nothing, so x dev on the tree it just wrote fails with X_BUILD_FAILED. The script installs the dependencies, writes .env.development.local, generates and applies the first migration, and seeds — idempotent, so it is safe to re-run after every pull.

Thin wrapper over x new — same templates, same flags, no second code path.

| Flag | Does | |---|---| | --dir <path> | parent directory (default: cwd) | | --no-example | skip the example feature slice | | --dry-run | print the file list, write nothing | | --json | machine-readable output |

What you get: apps/web/{site,app,api,shared}, apps/admin with MCP on, apps/{mobile,desktop} placeholders, packages/{domain,db,i18n,ui,mcp}, bin/, docker/, app.config.ts — a landing page at 0kb JS, a streaming authed dashboard, a seeded database and x verify green.