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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@themranderson/gitpuller

v1.0.0

Published

A Node.js tool to pull updates for specified branches in multiple git repositories

Readme

GitPuller

A Node.js cross-platform CLI tool to automatically pull updates for specified development branches in multiple git repositories, configurable per repository.

Installation

  1. Ensure Node.js is installed.
  2. Clone or download this project.
  3. Run npm install to install dependencies (including ESLint for linting).

Development

  • Run npm run lint to check code style with ESLint.
  • Run npm run lint:fix to automatically fix linting issues.
  • The project uses .editorconfig for consistent formatting. Ensure your editor supports it.

Usage

After installing globally (npm install -g @themranderson/gitpuller), run:

gitpuller

Or locally:

npm start
# or
node index.js

To specify a custom config file:

gitpuller --config /path/to/my-config.json

For help:

gitpuller --help

Publishing

This package is automatically published to npm via GitHub Actions on pushes to the master branch as @themranderson/gitpuller. To set up publishing:

  1. Create an npm account if you don't have one.
  2. Generate an access token with publish permissions.
  3. Add the token as NPM_TOKEN in your repository's secrets (Settings > Secrets and variables > Actions).

Configuration

Edit config.json:

  • rootPath: The root directory containing your git repositories.
  • repos: An object mapping repository folder names to their development branch names.
  • additionalRepos (optional): An array of objects with path and branch for repos outside rootPath.
  • switchToBranch (optional): Boolean, default false. If true, switch to the configured branch if not already on it (with stashing and popping).

Example:

{
  "rootPath": "/path/to/your/repos",
  "switchToBranch": true,
  "repos": {
    "my-repo": "main",
    "another-repo": "develop"
  },
  "additionalRepos": [
    {
      "path": "/full/path/to/repo/folder",
      "branch": "main"
    }
  ]
}

Usage

Run the tool:

npm start

Or:

node index.js

The tool will:

  • Scan for git repositories under rootPath (up to depth 2).
  • For each repository listed in repos, switch to the specified branch (stashing changes if necessary), pull updates if available, and switch back.

Behavior

  • Only configured repositories are processed.
  • If you're already on the development branch, it will pull if there are remote changes.
  • If on a different branch, it stashes local changes, switches to the dev branch, pulls, switches back, and pops the stash.
  • Errors are logged but don't stop processing other repos.

Cross-Platform

Works on Windows, Linux, and macOS, using Node.js built-in modules.