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 🙏

© 2024 – Pkg Stats / Ryan Hefner

cox

v1.1.4

Published

git commander for multi-repositories

Downloads

25

Readme

cox

CLI commander for developing with multiple submodules, each with their own Git repository. Cox runs both Git and NPM-related tasks on the project source folder, as well as all the versioned submodules.

As such, a "cox checkout " should be seen as : check out branch in the project root, AS WELL as in all the submodules' repositories. This allows you to create a new feature (one that might affect contents in multiple submodules) recursively in a single command (see "cox start").

All Cox commands should be run from the root of the main project.

Installation

npm install -g cox

Usage

Install

cox install

installs all the project modules, defined in package.json coxDependencies, like:

  "coxDependencies": {
    "some-lib": "[email protected]:username/some-lib.git",
    "some-other-lib": "[email protected]:username/some-other-lib.git",
  }

Then runs npm install on these repositories too.

update

cox update

runs npm update in the project folder and in all submodules

Start

cox start <branchName>

Start developing on a new branch with given name 'branchName', the new branch will be branched off 'develop' by default.

cox start <branchName> <sourceBranch>

Start developing on a new branch with given name 'branchName', the new branch will be branched off 'sourceBranch'.

checkout

cox checkout <branchName>
//or to checkout a new branch:
cox checkout -b <branchName>

Change to another branch

reset

cox reset

runs 'git reset --hard'.

pull

cox pull

GIT pulls the latest changes in the current branch.

status

cox status

displays the GIT status of all repos

diff

cox diff

displays the GIT diff of all repos

add

cox add

runs git add to all files unstaged in all repos

commit

cox commit "<message>"

commits staged changes to all the repos with given message

push

cox push <branchName>

GIT pushes the latest changes in the current branch to origin

kill

cox kill <branchName>

checks out develop, kills the branch locally and kills the branch remotely on origin (!)

Please use Cox responsibly, don't forget to use protection.