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

procedures

v1.1.0

Published

******

Downloads

115

Readme


This module is provided on behalf of the
Rhetorically Elloquent Advanced Development Moves Ensemble
for the pursuit of intergalactic mercantile diplomas.


procedures

tutorial


dates

import { rhythm_filter } from 'procedures/dates/rhythm-filter'

const RF = rhythm_filter ({
	// every 500 milliseconds
	every: 500
});

function window_size_changed (event) {
	RF.attempt (({ ellipse, is_last }) => {
		// ellipse = new Date ()
		
		console.log ("window size changed", { event })
	});
}

window.addEventListener ("resize", window_size_changed);
// window.removeEventListener ("resize", window_size_changed)
Example:
	With:
		const RF = rhythm_filter ({
			// every 500 milliseconds
			every: 500
		});

	Given an array of calls at:
		[ 0, 200, 600, 900, 1200, 1300, 1400 ]


	This is what happens; 
	however, the clock might be off by a few milliseconds:
	
		0 is called at 0 milliseconds and the filter is in place until 500 milliseconds,
		200 is filtered,
		
		600 is called at 600 milliseconds and the filter is in place until 1100 milliseconds,
		900 is filtered,
		
		1200 is called at 1200 milliseconds and the filter is in place until 1700 milliseconds,
		1300 is filtered,
		
		1400 
			is called at around 1700 milliseconds, 
			since another call did not take place
			between 1200 and 1700.
			It then starts filtering until 1900 milliseconds.

furnish

These functions should always return the type denoted.

This function always returns a string.

import { furnish_string } from 'procedures/furnish/string'
furnish_string ({ 's': '1' }, [ 's' ], '')

This function always returns a array.

import { furnish_array } from 'procedures/furnish/array'
furnish_array ({ 's': '1' }, [ 's' ], '')

This function always returns a dictionary.

import { furnish_dict } from 'procedures/furnish/dict'
furnish_dict ({ 's': '1' }, [ 's' ], '')

object

import { has_field } from 'procedures/object/has_field'
has_field ({ "s": 1 }, "s")