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

devops-custom

v1.0.4

Published

Auto-update daemon para proyectos Node con Git + PM2

Readme

devops-custom

Auto-update daemon for Git repositories with optional build and restart steps.

Global Install Readiness

Current package status is compatible with global usage (npm i -g devops-custom):

  • bin is defined in package.json as devops-custom -> dist/cjs/cli.js.
  • Compiled artifacts are present under dist/ and included in package tarball.
  • CLI entrypoint includes Node shebang (#!/usr/bin/env node).

Features Available Today

  • Scans a root directory for Git repositories.
  • Includes reposRoot itself if it has a .git folder.
  • Sequential polling (no parallel repo updates).
  • Fetch + incoming commit detection with HEAD..remote/branch.
  • Pull, optional build, optional restart.
  • Per-repo config via .devops-custom.json.
  • Build-only command for one repository.

Usage Modes

1) Use it globally (parameters)

Install globally:

npm i -g devops-custom

Run daemon using CLI parameters:

devops-custom start \
  --poll-interval 60000 \
  --repos-root /absolute/path/to/projects \
  --log-level info \
  --load-bashrc true \
  --bashrc-path ~/.bashrc

Other global commands:

devops-custom scan --repos-root /absolute/path/to/projects
devops-custom build --repo-path /absolute/path/to/repo
devops-custom status

2) Use it cloned (with .env)

Clone and run locally with .env defaults:

git clone <your-repo-url>
cd devops-custom
yarn install
cp .env.example .env

Example .env:

POLL_INTERVAL=300000
REPOS_ROOT=~/projects
LOG_LEVEL=info
LOAD_BASHRC=true
BASHRC_PATH=~/.bashrc

Run from source:

yarn dev start

Optional local commands:

yarn dev scan
yarn dev build --repo-path ~/my-repo
yarn dev status

3) Use it as a dependency (parameters)

Install in another project:

npm i devops-custom

Start polling from your own code using explicit params:

import { Poller } from 'devops-custom';

async function main() {
  const poller = new Poller();

  await poller.start({
    pollInterval: 60_000,
    reposRoot: process.cwd(),
    logLevel: 'info',
    loadBashrc: true,
    bashrcPath: '~/.bashrc',
  });
}

main().catch((error) => {
  console.error(error);
  process.exit(1);
});

Repository Config (.devops-custom.json)

Create this file inside each repository you want to control:

{
  "branch": "master",
  "remote": "origin",
  "build": "yarn install && yarn build",
  "restart": "pm2 restart my-app",
  "pm2": true,
  "autoUpdate": true,
  "enabled": true
}

If the project does not use PM2:

{
  "branch": "master",
  "remote": "origin",
  "build": "yarn install && yarn build",
  "pm2": false,
  "enabled": true,
  "autoUpdate": true
}

Runtime Rules

  • If configured remote does not exist, pull is skipped.
  • If no pull happens, restart is skipped.
  • If no build runs, restart is skipped.
  • Runtime commands (yarn, npm, pnpm, node, bun, deno, etc.) are skipped for non Node/Deno/Bun repos.

Exports

  • Poller
  • Scanner
  • Worker
  • Shared types from src/types.ts

Development

yarn test
yarn build:cjs
yarn build:esm
yarn build

AI Notice

Parts of the documentation and test code in this repository were generated with AI assistance and then reviewed and adjusted during development.