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

@xiaomingio/tinyship

v0.1.9

Published

Tiny deploy/runtime toolkit for Node.js and PM2 projects.

Readme

@xiaomingio/tinyship

CLI package for TinyShip. It validates and deploys Node.js / PM2 projects by syncing configured files to remote hosts, installing production dependencies, and reloading matching PM2 services.

For full project documentation, see the repository README: https://github.com/xiaomingio/tinyship-js.

Installation

npm install -D @xiaomingio/tinyship

For PM2 services, use standard NODE_ENV=production and Node's native --env-file. TinyShip reads the env path from PM2 node_args, falling back to .env.production inference, and validates that the file is included in rsync; application code only reads process.env.

Hosts use ecosystem.config.cjs by default and can select another PM2 config with host.ecosystem. Services match PM2 apps by service key by default and can target an existing app name with service.pm2App. This supports staging or device-specific startup configuration without custom PM2 post commands.

Put shared deploy paths in host.rsync and app-specific paths in service.rsync. TinyShip merges and deduplicates selected paths, then runs rsync once per host.

For existing PM2 processes, TinyShip first verifies that each same-name process belongs to the selected host appDir. It reloads unchanged services in one command, recreates only services whose PM2 topology changed, starts missing services, and saves the resulting PM2 process list once.

Use service.preCommand for remote commands that must run after rsync/npm install and before PM2 starts or reloads, such as database migrations from newly uploaded code. Set service.stopForPreCommand: true to stop the selected PM2 services before those commands; postCommand still runs after PM2 is back.

Commands

| Command | Purpose | | --- | --- | | tinyship validate | Validate config, PM2 apps, env files, and local upload paths | | tinyship preflight | Check SSH, remote tools, directory permissions, and local rsync | | tinyship deploy | Print usage plus configured hosts and services without deploying | | tinyship dry-run host <hostName> | Preview deployment commands for one host | | tinyship dry-run service <serviceName> | Preview deployment commands for one service | | tinyship dry-run all | Preview deployment commands for all hosts | | tinyship deploy host <hostName> | Deploy one host and all services on it | | tinyship deploy service <serviceName> | Deploy one service | | tinyship deploy all | Deploy all hosts in config order |

License

ISC