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

@freewrite-cms/cli

v0.2.0

Published

Scaffold a documentation site powered by @freewrite-cms/framework — pick a theme, get a deployable Next.js project.

Readme

@freewrite-cms/cli

Scaffold a documentation site powered by @freewrite-cms/framework — pick a theme, get a deployable Next.js project. Like npx shadcn, but for docs.

npx @freewrite-cms/cli@latest init my-docs

What it does

  1. Asks where to create your project (or takes a directory argument). If that folder already exists and isn't empty, it moves the current contents into existing-contents/ (and tells you), so nothing is overwritten.
  2. Asks which theme you want — Aurora, Fern, Cedar, Mono, or Base.
  3. Downloads that theme as a standalone Next.js app.
  4. Optionally wires up your OpenAPI spec (path or URL) so the API Reference is generated from it. API docs are OpenAPI-first; everything else is MDX.
  5. Prints the next steps and points you at the project's deploy guide.

Usage

npx @freewrite-cms/cli@latest init [directory] [options]

| Option | Description | | --- | --- | | -t, --theme <name> | aurora | fern | cedar | mono | base | | -o, --openapi <src> | path or URL to an OpenAPI spec for the API Reference | | --from <dir> | scaffold from a local templates directory (development) | | -y, --yes | accept defaults, skip optional prompts | | -h, --help | show help |

Examples

# interactive
npx @freewrite-cms/cli@latest init

# pick everything up front
npx @freewrite-cms/cli@latest init docs --theme mono

# generate the API Reference from your spec
npx @freewrite-cms/cli@latest init api-docs --theme fern --openapi https://example.com/openapi.json

Then:

cd my-docs
npm install
npm run dev

Open http://localhost:3000. Each scaffolded project ships a README with content and deployment guides (Vercel + AWS Amplify).

License

MIT.