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

gcr

v3.0.0

Published

A node gitlab-ci-runner

Downloads

15

Readme

gcr

Build Status

A node gitlab-ci-runner

Install

$ npm install -g gcr

Usage

The first time you run gcr, just run gcr without a token. It will prompt your for your registration token and will then generate your CI token.

$ gcr --help

gcr - a gitlab ci runner

    Usage:

      gcr [options]

    Options:

      -h, --help                  show help and usage
      -l, --loglevel <level>      set log level
      -v, --version               show version
      -u, --url <url>             set ci server url
      -t, --token <token>         set registration token
      -T, --timeout <number>      set global test timeout in seconds
      -b, --buildDir <dir>        set the build directory
      -s, --strictSSL             enable/disable strict ssl
      -n, --npm                   run npm install/test if no commands are present
      -k, --keypath <path>        specify path to rsa key

Why?

I wanted something that was really easy to install (npm install -g gcr)

License

MIT (See LICENSE for more info)

Thanks

Thanks to the GitLab team for all of their effort on GitLab/GitLab CI.

Notes

On launch, if a rsa key does not exist (named gcr.pub), then one will automatically be created. gcr will then ask for your GitLab CI Coordinator URL as well as your Registration Token. The directory in which projects are built defaults to /tmp/builds. If you would like to change that, then simply run gcr --buildDir <dir> and that will be saved.

gcr remembers your config by adding a json file to ~/.config/gcr.js