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

wsinit

v1.0.1

Published

Initialize workspace by cloning all repos from organization or user

Downloads

3

Readme

Workspace Init

Clones all repositories, public or private, of a specified user or organization.

Credentials are needed, they are present in a file named .wsinit.json place in the home folder.

Installation:

~$ sudo npm install -g wsinit

Usage:

For user:

~$ wsinit --name <github username>

For organization:

~$ wsinit --org --name <github organization>
The description is used to determine the exact path to which the repository will be cloned.
If the description is empty, or if it contains spaces, the default path is used, ./<repository name>.

Examples:

Repository description: path/to/folder -> Will clone the repository in ./path/to/folder/<repository name>

Repository description: Some description -> Will clone the repository in ./<repository name>

Empty repository description -> Will clone the repository in ./<repository name>

Authentication:

The following file, .wsinit.json, must be placed in the home folder and is required for authentication with the GitHub API:
If you only want to clone public repositories:
{
  "user": <github username>
}
If you want to clone private repositories as well:
{
  "user": <github username>,
  "at": <github API access token>
}
To run the tests as well, the file must look like this:
{
  "user": <github username>,
  "at": <github API access token>
  "test_repo_1": {
    "name": <repo name>,
    "full_name": <repo full name>
    "local_path": <local path to which the repo will be cloned>
  },
  "test_repo_2": {
    "name": <repo name>,
    "full_name": <repo full name>
    "local_path": <local path to which the repo will be cloned>
  }
}
You can place the file yourself or you could run ~$ wsinit --cred which will prompt for user name and Github API access token.
~$ wsinit --cred
If you try to use the script without the .wsinit.json file present in the home folder, you will be prompted to initialize it, and execution will continue after the file is created.
Note: You could omit the access token. The script will still work but only for public repositories.
Note: The tests clone the repositories in the test folder(wsinit/test). Tests do not delete anything.