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

gitlab-init

v1.0.4

Published

Clones all the repositories you have access to (unless they already exist)

Downloads

15

Readme

gitlab-init

A simple CLI tool that connects to your Gitlab installation, lists all projects you have access to and attempts to git clone them into the same folder structure as in Gitlab.

Why on earth would you need this?

  • When installing a new machine and wanting to get a quick start
  • Getting new people joining your team quickly set up
  • Use a unified directory structure for everyone
  • When you just want to git clone all Gitlab projects

Installation

  1. Install git and node
  2. npm -g install gitlab-init
  3. mkdir projects
  4. gitlab-init -e https://your-gitlab-url -t your-token
  5. Success!

Usage

Usage: gitlab-init [options]

Options:
  -V, --version           output the version number
  -e, --endpoint [url]    Gitlab installation endpoint
  -t, --token [string]    Your Gitlab profile token (Can be provided as env: GITLAB_TOKEN)
  -m, --max <n>           Maximum project pages to get (10 per page) [10] (default: 10)
  -p, --path [directory]  Root projects directory where the project will be cloned into (default: "./projects/")
  -h, --help              output usage information