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

v31.49.0

Published

bunx create-ultimate myapp — scaffold an Ultimate monorepo

Downloads

17,440

Readme

create-ultimate

Scaffold an Ultimate app — the monorepo, a seeded database and a green gate — with one command.

bunx create-ultimate myapp && cd myapp && bun run setup && bun run dev

Guide: Getting started.

bun run setup is the scaffold's own script (bin/setup.ts, run by Bun — the same command in PowerShell, cmd and bash) 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, seeds, and writes x.manifest.json — six commands, 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) | | --shape <shape> | start from an app shape — api, blog (Shapes); never with --no-example | | --no-example | skip the example feature slice | | --no-git | leave a bare directory; do not git init and commit | | --dry-run | print the file list, write nothing | | --force | write into a directory that already exists, holds no app.config.ts and none of the paths the scaffold writes (a fresh clone: .git, a LICENSE); one taken path (README.md, package.json, …) refuses the run with X_GENERATE_CONFLICT naming them, nothing written — never an overwrite | | --json | machine-readable output |

Opening a repro bundle

bunx create-ultimate repro bundle-req1.json --framework ../ultimate

A bug's x repro <id> --bundle file, opened into a scratch app repro-<id>/: the x new scaffold (no example slice), the test under repro/ importing the scratch app's db package, the bundle as repro/bundle.json. A bundle is untrusted input — an issue attachment from anyone: only its subject is read, checked field by field, and the test is rendered from it; the bundle's own reproducer text is never written or run. With a framework checkout — --framework <path>, or the one cwd is inside — every @ultimat3/* is a file: override onto its source. repro with no file is still an app named repro. A file that is no x-repro-bundle/1 bundle is X_REPRO_BUNDLE_INVALID; a directory that exists is X_CLI_BAD_FLAG. It takes --dir (the parent, default cwd), --framework (the checkout to link; none found → the registry) and --json — kept out of the table above, which is x new's flags and nothing else.

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.