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

@digitalscientists/poller

v1.1.3

Published

a fetch and poll reference implementation and maybe module

Readme

Poller - the best thing since sliced bread

This is a simple little library that implements a fetch-and-poll procedure.

Getting Started

npm install @digitalscientists/poller

Usage


const fetchAndPoll = require("@digitalscientists/poller") 

const options = {
  url: "https://a-url-that-supports-polling.com/begin",
  pollUrl: (id) => `https://a-url-that-supports-polling.com/check/${id}`, // or whatever format
  wait: 2000, // how long to wait between polling (optional, defaults to 2 seconds)
  timeout: 120000, // how long to wait between polling (optional, defaults to 120 seconds)
  payload: {
    the: "payload",
    for: "the initial POST"
  }
}

const response = await fetchAndPoll(options)

Deployment

Make sure you run the tests before deploying

npm build

npm version patch # or major|minor depending on changes

npm publish

Development

npm i

npm run debug:test

Make sure you have NiM installed in chrome for best results.

You can also run npm link if ya know what you're doing. This will let you install the local dev version in a separate app. Google that for more info.

Tests

npm test

This will run the rollup build process and test the main index.js file as well as the built lib files agaist a mock server. TODO: still need to test the UMD version, but need a browser env or something for that.

current assumptions and limitations

The library currently assumes the following:

  • the initial fetch will be a POST call
  • the initial fetch will return something that looks like {id: "somekindaideitherastringorinteger", status:"queued"}
  • subsequent polling will be GETs
  • statuses for polling are: queued, done, and errored
  • erroring jobs will not be retried
  • everything is json. if you want xml, you're fired