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

@klyper/cli

v0.3.0

Published

Command line tools for the Klyper monorepo.

Downloads

23

Readme

@klyper/cli

Command line tools for managing the Klyper monorepo.

Commands

npm run build --workspace @klyper/cli
npm run check --workspace @klyper/cli
npm run lint --workspace @klyper/cli
npm test --workspace @klyper/cli

build uses Rollup for the package output. check runs TypeScript without emitting files.

Create a Package

Create a new package template:

npm exec klyper create package utils

Alternative syntax:

npm exec klyper package create utils

The command creates packages/utils with:

  • package.json
  • tsconfig.json
  • README.md
  • src/index.ts
  • src/index.test.ts

The generated package.json follows the public package convention used by the monorepo:

  • main points to the CommonJS bundle at ./dist/index.cjs
  • module and exports.import point to the ESM bundle at ./dist/index.js
  • types and exports.types point to ./dist/index.d.ts
  • exports.require points to the CommonJS bundle
  • sideEffects is false
  • prepublishOnly runs npm run build && npm test

The root build runs each package through npm workspaces, so new packages do not need root TypeScript project references.

Use a custom scope:

npm exec klyper create package auth --scope @klyper