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

cloneman

v1.1.0

Published

Application template and lifecycle management tool

Readme

cloneman

Template manager for Node applications and libraries. 🐢

Usage for consumers

Available commands

  • Create
  • Update

Create a new application based on a template

npx cloneman create my-new-application template-package-name

Keep in mind that template-package-name needs to be published to the npm registry.

You can also refer to a local template file: npx cloneman create my-new-application ../directory/template.tgz

Update your application

Note: You can only update your application using the same template it was created with.

To the latest version: npx cloneman update

You can also update to a specific version: npx cloneman update 1.2.3

Local tarball

As with the create command, you can also point to a local tarball: npx cloneman update ../directory/template.tgz

Usage when creating and managing templates

The best way to understand how a template is defined is to check the example template in ./fixtures/base-template.

A template is required to have:

.cloneman
├── build.mjs
└── cloneman.json

cloneman.json

Contains a list of managed files that will be used when creating and updating an application.

{
    "managedFiles": ["managed.txt"],
    "ignoredDependencies": []
}

managedFiles

List of files owned by the template. These files will be overwritten when updating your application.

ignoredFiles

List of files to exclude when creating a template. Supports exact file names or glob patterns, e.g. test/* to remove all test files.

ignoredDependencies

List of dependencies to exclude when creating a template. Supports exact package names or glob patterns, e.g. @fkui/* to remove all dependencies in the @fkui scope.

build.mjs

Build script to prepare an application or library to be a cloneman template.

Available commands when working with templates

Both commands requires to be called insisde a template folder.

  • Publish
  • Pack

Publish

npx cloneman publish

Publish a new template version to the npm registry. (i.e npm publish)

Pack

npx cloneman pack

Creates a local tar file of your template. (i.e npm pack)

Development

npm install
npm run build
npm test