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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@lbennett/transient-tantrum

v1.1.0

Published

Target a GitLab CI job to retry N times to find transient failures.

Readme

@lbennett/transient-tantrum

Target a GitLab CI job to retry N times to find transient failures.

This CLI tool is intended to be used for MRs that include potential fixes for transient failures on GitLab CI.

If you think you have found a fix for a transient failure, you can retry the job a number of times to increase your confidence in the fix. This does replace debugging and understanding the fix.

As of v1.1.0, you can also invert the operation and retry on failure instead of success. This was not the original intended use, but it comes in handy with known flaky tests that have no immediate fix where all you can do is retry until your pipeline is green.

Installation

npm install --global @lbennett/transient-tantrum
#OR
yarn global add @lbennett/transient-tantrum

Usage

First you must create a GitLab personal access token.

GITLAB_PRIVATE_ACCESS_TOKEN=YOUR_GITLAB_PRIVATE_ACCESS_TOKEN transient-tantrum <projectPath> <mergeRequestId> <jobName> [retryCount] [-wivh]
  • projectPath: The namespace name and project name, separated by a slash. e.g. gitlab-org/gitlab-ce
  • mergeRequestId: The Merge request ID. e.g. 23033
  • jobName: The name of the job to test for transients. e.g. karma
  • retryCount: The number of times you would like to retry the job on success. Default: 5
  • waitDuration: The duration in minutes to wait between checking the job status. Default: 3
  • invert: Retry on failure instead of success Default: false
$ transient-tantrum -h
transient-tantrum <projectPath> <mergeRequestId> <jobName> [retryCount]

start a transient tantrum on a specific job for a given merge request

Positionals:
  projectPath     Path to the project containing the MR to test e.g.
                  gitlab-org/gitlab-ce.
  mergeRequestId  ID of the Merge request to test e.g. 1234.
  jobName         Name of the job to retry, e.g. karma, or "docs lint".
  retryCount      Number of times to retry the job if it succeeds                   [default: 5]

Options:
  --version          Show version number                                             [boolean]
  -w, --waitDuration The duration in minutes to wait between checking the job status [number] [default: 5]
  -i, --invert       Retry on failure instead of success                             [boolean] [default: false]
  -h, --help         Show help                                                       [boolean]

Example

$ transient-tantrum gitlab-org/gitlab-ce 23033 karma 1


Starting tantrum...


Getting latest pipeline for gitlab-org/gitlab-ce!23033...
Getting pipelines for gitlab-org/gitlab-ce!23033...
Finding karma job...
Getting jobs for pipeline #36508658...
Getting jobs for pipeline #36508658...
Getting jobs for pipeline #36508658...
The karma jobs status is currently "running".
Checking pipeline in 3 minutes...
Getting job...
The karma jobs status is currently "running".
Checking pipeline in 3 minutes...
Getting job...
The karma jobs status is currently "running".
Checking pipeline in 3 minutes...
Getting job...
The karma jobs status is currently "running".
Checking pipeline in 3 minutes...
Getting job...
The karma jobs status is currently "success".
Retrying job...
Checking pipeline in 3 minutes...
Getting job...
The karma jobs status is currently "running".
Checking pipeline in 3 minutes...
Getting job...
The karma jobs status is currently "running".
Checking pipeline in 3 minutes...
Getting job...
The karma jobs status is currently "running".
Checking pipeline in 3 minutes...
Getting job...
The karma jobs status is currently "success".
Tantrum complete.
✨  Done in 1465.05s.