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

liblooper

v1.0.0

Published

Looper implementation for use in conjonction with the HJS-MESSAGE messaging API. This is the browser version of the

Downloads

7

Readme

LIBLOOPER

Looper implementation for use in conjonction with the HJS-MESSAGE messaging API. This is the browser version of the looper.

Looper classes: Looper, MessageLooper.

Installation

Node:

npm install liblooper --save

Usage

The Looper is used to run messages synchronized with animation frames. requestAnimationFrame by default do not have a message loop associated with them; to create one, call Looper.createLoopHandler in the script that is to run the loop.

Most interaction with a message loop is through the MessageLooper that is a subclass class of MessageHandler.

Your can create any number of MessageLooper's but only one loop is running in the entire application. But it's recommanded to use only one global instance of Looper.

Create a MessageLooper
import {Looper} from 'liblooper';

// this create an instanceof MessageHandler that run in the loop
let ML = Looper.createLoopHandler({
    
    fps: 40 /* An optional FPS is accepted (60 is default) */,
    
    quitAllowed: false /* An optional quit flag is accepted (true is default) */,
    
    handleMessage(msg) {
        // enter frame here
        // handle messages interactions
        return true;
    },
    
    handleRender(interpolation) {
        // render frame here
        // handle drawing on canvas for ex.
    },
    
    handleExit(fps, panic=false) {
        // exit frame here
        // clean code for example
    }

});
Pause/Resume/Exit from a loop
import {Looper} from 'liblooper';

const START_CMD = 0xffddcc;
const PAUSE_CMD = 0xffddcd;
const RESUME_CMD = 0xffddce;
const EXIT_CMD = 0xffddde;

// this create an instance of MessageLooper that run in the loop
// All parameters accepted by a MessageHandler are accepted by MessageLooper's
let ML = Looper.createLoopHandler({
    
    handleMessage(msg) {
        let what = msg.what;
        switch(what) {
            case START_MSG:
                this.sendEmptyMessage(PAUSE_CMD);
                break;
            case PAUSE_CMD:
                this.pause();
                // now messages are sending only with the message queue
                // handle render and handle exit are no more called
                this.sendEmptyMessage(RESUME_CMD);
                break;
            case RESUME_CMD:
                this.resume();
                // now messages are sending throw the loop
                // handle render and handle exit are called
                this.sendEmptyMessage(EXIT_CMD);
                break;
            case EXIT_CMD:
                this.exit();
                break;
        }
        return true;
    },
    
    handleRender(interpolation) {
        console.log(interpolation);
    },
    
    handleExit(fps, panic=false) {
        console.log(fps);
    }

});

ML.sendEmptyMessage(START_MSG);

Contacts

Aime - [email protected]

Distributed under the MIT license. See LICENSE for more information.