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

fertilize

v0.1.0

Published

retry the same thing, expect different results

Downloads

3

Readme

fertilize -- retry the same thing, expect different results

SYNOPSIS

Sometimes spawning a child process is not successful. This attempts to fertilize the process by being stubborn, retrying a number of times before eventually giving up. Therefore this isn't quite the same as "crazy", which people like to quote.

MOTIVATION

The following is just a use-case. Retrying stuff can be justified / useful, even with computers...

Sometimes (and in some cases often) rsync will fail to sync (due to "Broken pipe" or something). There is a known bug the solution for which is to keep retrying... That's exactly what this script does.

Call it like you otherwise would rsync. The only difference being that if you pass a number as the very first argument, it will run that many number of times. If you give it 0, it will run forever until done. If no number is provided, it will use some hardcoded default, which supposedly has better chances than the otherwise usual rsync once.

EXAMPLE

fertilize 3 rsync something /dev/null

Spawns rsync something /dev/null and probably fails 3 times in a row. It could be because the something is missing or /dev/null doesn't allow it.

Be careful with fertilize 0 something - it easily becomes an infinite loop... So be convinced the something is likely to exit with a status of 0. Zero (being success) is fitting for an exit, it otherwise goes on for infinity.

INSTALL

With the npm prerequisite, do npm install -g fertilize.

LICENSE

This is free and unencumbered public domain software. For more information, see http://unlicense.org/ or the accompanying {file:UNLICENSE} file.