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

@zenness/create

v0.3.2

Published

Create a new zenness project — `npm create @zenness`, or the pnpm/yarn/bun spelling of it.

Readme

@zenness/create

npm create @zenness
pnpm create @zenness
yarn create @zenness
bun create @zenness

A thin shim so those spellings work. It forwards to zn init from the @zenness/cli package, which is where the CLI and the install flow actually live.

Why the bare scope

npm create <x> normally runs create-<x>. A scope on its own is the exception: npm create @zenness resolves @zenness/create. That is why this package is named create, and why its bin is too — npm looks for a bin matching the package's unscoped name.

Shorter spellings of the same request: create-zn (npm create zn) and create-zenness (npm create zenness). All three forward to runCreate() in @zenness/cli, so there is one install flow rather than three copies of one.

Use @zenness/cli directly if you want the other commands (dev, build, preview).