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

underverse

v0.1.1

Published

underverse is simple backlog management and administration module

Downloads

13

Readme

Underverse

Underverse is a small backlog/queue manager that detects when items in your backlog are out of sync and issues a fetch event to retrieve the missing items. This module makes the following assumptions about your backlog of data:

  • The backlog works with a bag of a ids.
  • The ids a nummeric which equals the position of the backlog.
  • The ids are ordered.
  • The backlog has limit.
  • The backlog resets it's ids once the limit is reached.

Build status

Build Status

Installation

The installation is done through npm

npm install underverse --save

Add the --save if you want to save the module in your package.json.

Usage

The module is initialized with the size of the backlog;

var Underverse = require('underverse')
  , uv = new Underverse(1000);

The snippet above creates a new underverse that works with a backlog that can contain 1000 items. You should set the initial id of log. For example if your queue is filled with 100/10000 slots:

uv.cursor(100);

As it could be possible that your messages get out of sync if you use a remote backlog (for example a reconnect) you can listen to the fetch event to know which ids are missing.

uv.on('fetch', function (missing, mark) {

})

The fetch event receives 2 arguments, an array of missing id and a mark function. The mark function allows you set all ids in to a fetching state so you won't retrieve duplicate fetch calls that retrieve the same information. If you call the mark function with a boolean true it will mark all missing ids as received.

When you have received a message from your backlog call the uv.received() method with the id.

uv.received(10)

and that's it. Take a look at the tests for some examples.

License

MIT