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

@linnify/cli

v0.10.0

Published

CLI tool to pull boilerplate from the Linnify starter repository

Readme

@linnify/cli

CLI tool that pulls boilerplate from the Linnify starter repository.

Installation

pnpm add -g @linnify/cli

Or run directly:

pnpm dlx @linnify/cli boilerplate --help

Prerequisites

  • GitHub CLI installed and authenticated (gh auth login)
  • Access to the linnify/linnify-starter private repo

App Starters

| Type | Default name | Stack | |------|-------------|-------| | web | web | Next.js 16, React 19, App Router, ShadCN, better-auth | | api | api | Fastify, Zod | | job | job | Node.js background jobs with tsx | | mobile | mobile | Expo, React Native, Expo Router, NativeWind |

Run linnify list (alias linnify apps) to print this table from the CLI.

Commands

Boilerplate

Pull the full monorepo boilerplate with selected app starters. Each --app flag takes a JSON object with name (target folder inside apps/) and app (starter to use).

linnify boilerplate \
  --app='{"name":"web","app":"web"}' \
  --app='{"name":"admin","app":"web"}' \
  --app='{"name":"jobs","app":"job"}' \
  --app='{"name":"mobile","app":"mobile"}'

This copies the entire boilerplate (root configs, packages/, .github/, etc.) into the current directory, and creates only the selected apps inside apps/:

| --app value | Result | |---------------|--------| | {"name":"web","app":"web"} | apps/web/ using the web starter (Next.js) | | {"name":"admin","app":"web"} | apps/admin/ using the web starter (Next.js) | | {"name":"jobs","app":"job"} | apps/jobs/ using the job starter (background jobs) | | {"name":"api","app":"api"} | apps/api/ using the api starter (Fastify) | | {"name":"mobile","app":"mobile"} | apps/mobile/ using the mobile starter (Expo) |

Flags

| Flag | Description | |------|-------------| | --app <json> | App to include (repeatable) | | --force | Overwrite existing app directories | | --skip-install | Skip running pnpm install after setup | | --branch <b> | Pull from a specific branch (default: main) |

Development

pnpm install
pnpm dev boilerplate --help      # run in dev mode
pnpm build                       # bundle to dist/index.js
pnpm type-check                  # typecheck only

Adding new starters

Edit src/lib/config.ts — starters are listed in boilerplate.apps, each with its type, defaultName, and stack. The corresponding app folder must exist in the linnify-starter repository under apps/.

Publishing a new version

The package is published to the public npm registry as @linnify/cli.

Prerequisites: you must be logged in to npm with an account that has publish access to the @linnify org:

npm login

Steps:

  1. Bump the version in package.json following semver:

    | Change type | Command | |-------------|---------| | Bug fix | npm version patch | | New feature (backwards-compatible) | npm version minor | | Breaking change | npm version major |

    Or edit the "version" field manually.

  2. Publish — the prepublishOnly script builds automatically:

    npm publish
  3. Commit and push the version bump:

    git add package.json
    git commit -m "chore(cli): release v$(node -p "require('./package.json').version")"
    git push

Note: The package is scoped (@linnify/cli) and published with "access": "public", so no extra flags are needed.