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

manual-deploy

v2.0.0-beta.1

Published

Label A manual deploy script

Readme

Deploy script

Features

  • Version management
  • Automatic back-ups
  • Automatic server set-up

Usage

  • Install the package npm install --save-dev @labela/deploy
  • Create an deploy.sh in you project folder
#!/bin/bash
PROJECT= #PROJECTNAME

PROD_HOST= #PROD_HOST
ACC_HOST= #ACC_HOST

#Don't touch this
ENV=$1
source ./node_modules/@labela/deploy/index.sh
  • Change variables for your project
  • Make the file an executable $ chmod +x deploy.sh

Start the deploy by running the file with 1 argument that's the environment (TEST, ACC or PROD) $ ./deploy.sh TEST

Upgrading

To upgrade from version 0.5.4 and lower to ^6.0.0 you have to kill the old PM2 process. Previously all processes were named: server. The new process has the name of your project. Run pm2 kill server to terminate the old process.

All options to overwrite:

  • ROOT_USER - the user to login with ssh
  • TEST_PORT - default is 3000
  • TEST_HOST - default is 192.168.22.8
  • TEST_USER - default is PROJECT
  • ACC_USER
  • ACC_PORT - default is 3000
  • ACC_HOST
  • PROD_USER
  • PROD_PORT - default is 3000
  • PROD_HOST
  • STRAPI - default is false

Use caution when overwriting the following values:

  • PM2_CONFIG_NAME - default is pm2-server-config.json

Sentry

If you add a .sentryclirc file to the project root folder, it will also push a new release to Sentry after the deploy has been processed successfully. Read more about this in: https://gitlab.labela.nl/front-end/sentry-setup