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

git-seed

v0.0.7

Published

Git plugin to easily create, manage and replicate a composite clone

Downloads

21

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

nomilousnomilous

Keywords

Readme

objective

sudo npm install git-seed -g

Current version 0.0.6 (unstable)

git-seed

Todo

  • Follow symlinks
  • Switch to notice-0.0.11
  • Inform when switching submodule from git clone to subsequently published npm install (npm wont write into a node_modules folder already populated by git repo clone and vice-versa, best to leave the delete up to the user)
  • Inform on multiple nested same submodule on different revision. (This happens when the same unreleased node_module is a doublenested dependency in more than one nested submodule) or see tip

Usage

git seed --help

git seed init

Make/Update the .git-seed file


> git seed init

 info (start seed init) - recurse for git repositories in '.'
 info (found repo) - ./.git
 info (found repo) - ./node_modules/git-seed-npm/.git
 info (found repo) - ./node_modules/git-seed-npm/node_modules/git-seed-core/.git
 info (found repo) - ./node_modules/nezkit/.git
 info (found repo) - ./node_modules/notice/.git
 info (found repo) - ./node_modules/notice-cli/.git
EVENT [seed update] - wrote file: ./.git-seed

git seed clone

Clone all repos according to the .git-seed file

  • The .git-seed control file specifies the branch that each repo should be on.
  • Running a clone will checkout that branch

> git seed clone

 info (start seed clone) - for all git repositories in './.git-seed'
 info (skip) - already cloned .
 info (skip) - already cloned ./node_modules/git-seed-npm
 info (skip) - already cloned ./node_modules/git-seed-npm/node_modules/git-seed-core
 info (skip) - already cloned ./node_modules/nezkit
 info (skip) - already cloned ./node_modules/notice
 info (skip) - already cloned ./node_modules/notice-cli
EVENT [seed clone] - success
 info (seed clone results) - undefined
 info (shell) - run npm install, (in .)
 info (shell) - run npm install, (in ./node_modules/git-seed-npm)
 info (shell) - run npm install, (in ./node_modules/git-seed-npm/node_modules/git-seed-core)
 info (shell) - run npm install, (in ./node_modules/nezkit)
 info (shell) - run npm install, (in ./node_modules/notice)
 info (shell) - run npm install, (in ./node_modules/notice-cli)
EVENT [seed install] - success
 info (seed install results) - undefined

git seed status

Report status across all repos in the .git-seed file


> git seed status

info (start seed status) - for all git repositories in './.git-seed'
 info (has changes) - .
# On branch develop
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#   modified:   README.md
#
no changes added to commit (use "git add" and/or "git commit -a")

 info (skip) - no changes ./node_modules/git-seed-npm
 info (skip) - no changes ./node_modules/git-seed-npm/node_modules/git-seed-core
 info (skip) - no changes ./node_modules/nezkit
 info (skip) - no changes ./node_modules/notice
 info (skip) - no changes ./node_modules/notice-cli
 info (seed status) - success
 info (seed status results) - undefined

git seed commit

Commit with a common message across all repos with staged changes


> git seed commit -m 'commit uses pipeline'

info (start seed commit) - for any git repositories with staged changes in './.git-seed' 
 info (skip) - no staged changes .
 info (skip) - no staged changes ./node_modules/git-seed-npm
 info (shell) - run git --git-dir=./node_modules/git-seed-npm/node_modules/git-seed-core/.git --work-tree=./node_modules/git-seed-npm/node_modules/git-seed-core commit -m commit uses pipeline
 info (commit) - ./node_modules/git-seed-npm/node_modules/git-seed-core
[develop aa5c505] commit uses pipeline
 4 files changed, 117 insertions(+), 91 deletions(-)

 info (skip) - no staged changes ./node_modules/git-seed-npm/node_modules/git-seed-core
 info (skip) - no staged changes ./node_modules/nezkit
 info (skip) - no staged changes ./node_modules/notice
 info (skip) - no staged changes ./node_modules/notice-cli
 info (seed commit) - success
 info (seed commit results) - undefined

git seed pull

Pull across all repos

  • Pull first pulls the root repo to get the latest seed file
  • Pull only pulls other repos if their local version differs from that in the seed file

> git seed pull

info (start seed pull) - for all git repositories in './.git-seed'
 info (pull) - .
 info (shell) - run git pull git@github.com:nomilous/git-seed.git refs/heads/develop, (in .)
 info (seed pull) - success
 info (seed pull results) - undefined
 info (skip) - already up-to-date ./node_modules/nezkit
 info (skip) - already up-to-date ./node_modules/notice
 info (skip) - already up-to-date ./node_modules/notice-cli
 info (seed pull) - success
 info (seed pull results) - undefined
 info (shell) - run npm install, (in .)
npm http GET https://registry.npmjs.org/git-seed-npm/0.0.3
npm http 304 https://registry.npmjs.org/git-seed-npm/0.0.3
npm http GET https://registry.npmjs.org/git-seed-core/0.0.2
...
npm http 304 https://registry.npmjs.org/traverse
npm http 304 https://registry.npmjs.org/traverse
git-seed-npm@0.0.3 node_modules/git-seed-npm
└── git-seed-core@0.0.2 (when@2.1.0, fs-extra@0.6.1, findit@0.1.2)
 info (shell) - run npm install, (in ./node_modules/nezkit)
 info (shell) - run npm install, (in ./node_modules/notice)
 info (shell) - run npm install, (in ./node_modules/notice-cli)
EVENT [seed install] - success
 info (seed install results) - undefined

Tip

Got the same module nested again deeper inside another?

cd node_modules/
rm -fr notice/
ln -s phrase/node_modules/notice
cd ../
git seed status

 info (start seed status) - for all git repositories in './.git-seed'
 info (skip) - no changes .
 info (unpushed changes) - ./node_modules/notice
# On branch develop
# Your branch is ahead of 'origin/develop' by 47 commits.     <----------------SAME
#
nothing to commit (working directory clean)

 info (skip) - no changes ./node_modules/phrase
 info (unpushed changes) - ./node_modules/phrase/node_modules/notice
# On branch develop
# Your branch is ahead of 'origin/develop' by 47 commits.     <----------------SAME
#
nothing to commit (working directory clean)

 info (seed status) - success
 info (seed status results) - 

 ##
 cd node_modules/notice
 git push origin develop
 cd -
 git seed status
 info (start seed status) - for all git repositories in './.git-seed'
 info (skip) - no changes .
 info (skip) - no changes ./node_modules/notice
 info (skip) - no changes ./node_modules/phrase
 info (skip) - no changes ./node_modules/phrase/node_modules/notice
 info (seed status) - success
 info (seed status results) -