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

piggle

v6.1.0

Published

A library for processing generator javascript functions with automatic retries on transitory failures.

Downloads

30

Readme

Piggle

A simple mechanism for executing fragile (e.g. network or database reliant) functions.

npm

Define a long-running operation as an asynchronous javascript function. Pass that function to piggle to execute.

Piggle will automatically retry the function if a transitory error is raised using an exponential backoff strategy. The errors considered transitory and the backoff strategy can be configured.

There's a good piggle!

Example

In the example below, functions setValueOnService and setValueAtDatabase are async functions that call an external service and database respectively. We know they could fail due to temporary issues, so we wrap the calls using the retryable function exported from piggle.

import { retryable } from 'piggle'
import { setValueOnService, SomeNetworkError } from 'external-service'
import { setValueAtDatabase, SomeDatabaseError } from 'external-database'

async function doWork (newValue: string): Promise<void> {
  // You can determine which errors should be treated as transitory
  const isErrorTransient = err => err instanceof SomeNetworkError || err instanceof SomeDatabaseError || err.statusCode === 503

  // Each retry occurs after the given number of milliseconds, so the strategy below
  // would indicate calling the operation once immediately, a second time after 100ms,
  // a third after a further 200ms and a fourth and final time after a further 500ms.
  const retryStrategy = [100, 200, 500]
  
  // Processing continues until the retry strategy is exhausted or the canContinueProcessing
  // function returns false.  Typically this is used to stop operations because the host is
  // trying to shutdown.
  const canContinueProcessing = () => true

  // The connected functins setValueOnService and setValueAtDatabase can then be called
  // in sequence with a high chance of success because transitory errors will be bypassed.
  await retryable(() => setValueOnService(newValue), { isErrorTransient, retryStrategy, canContinueProcessing })
  await retryable(() => setValueAtDatabase(newValue), { isErrorTransient, retryStrategy, canContinueProcessing })
}

Installation

npm install piggle

Development

Code written in Typescript.

Testing

Tests are written using the Jest framework. 100% coverage is required.

npm test

Build

Type declarations are produced by the typescript compiler tsc. This is configured via the tsconfig.json file. Output is written to the /types folder and included in the published npm package.

A CommonJS lib is produced in the /lib folder.

npm run build

Continuous Integration and Deployment

Any pushes or pull-requests on non-master branches will trigger the test runner.

Any pushes to master will cause the library to be re-published.