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

gitlab-ci-trace

v0.1.2

Published

Output the trace for a gitlab ci job on push

Readme

gitlab-ci-trace

npm version

Output the results of CI job traces into the console that has pushed the commit. This mimics the behaviour users of Heroku are used to where by a push to heroku will trigger a build and the build status appears as part of the push status.

Features

  • Support for gitlab.com or custom deployments
  • Auto detects the GitLab host based on the ssh or https git url
  • Trace multiple simultaneous jobs
  • Auto detect the correct running jobs based on the HEAD commit hash

Usage

npm install -g gitlab-ci-trace

Unfortunately there is no functionality within git itself for a post push hook which is what we would like to hook onto. Instead we need to use a git alias.

You can choose to name the alias whatever you want. I chose git pusht for push and trace.

# ~/.gitconfig
[alias]
	pusht = !"git push $* && gitlab-ci-trace"

or

git config --global alias.pusht '!git push $* && gitlab-ci-trace'

You can also choose to just call the command directly after a push when you need to check on the status of a build.