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

royal-sampler

v2.0.0

Published

A lib for self-sampling code

Downloads

4

Readme

royal-sampler

For self-sampling code.

The Simpsons - Royal Sampler

Show your sorcery

import {execute} from 'royal-sampler'

function mySweetFunction () {
  return 'sweet';
}

let sampledFunction = execute(mySweetFunction).every(2).calls();
console.log(sampledFunction()); //undefined
console.log(sampledFunction()); //sweet

console.log(sampledFunction()); //undefined
console.log(sampledFunction()); //sweet

You can be slightly more DSL about it.

execute(mySweetFunction).every().call();
execute(mySweetFunction).every(5).calls();

What about time based sampling?

If your callback accepts a delta as the first parameter, then you can use a second set of helpers to have your code execute a set number of times per period.

function mySweetFunction (delta) {
  return 'sweet';
}

execute(mySweetFunction).every().millisecond();
execute(mySweetFunction).every().second();
execute(mySweetFunction).every().minute();
execute(mySweetFunction).every().hour();
execute(mySweetFunction).every(234).milliseconds();
execute(mySweetFunction).every(25).seconds();
execute(mySweetFunction).every(33).minutes();
execute(mySweetFunction).every(5).hours();

execute(mySweetFunction).about(1).timesPer.second();
execute(mySweetFunction).about(4).timesPer.minute();
var sampled = execute(mySweetFunction).about(7).timesPer.hour();

sampled(45);

Do I have to call my function

Yes. This package does not do any scheduling.

Is the delta important

Yes. We use that to determine when to call your function. If you said 1 time per second, after the sum of the delta reaches 1000, your code executes.

What about other variables

All variables get passed through to your function

function myFunction (delta, a, b, c) {
	console.log(a, b, c);
}

var sampled = execute(myFunction).every().second();
sampled(15, 1, 2, 3); // 1, 2, 3

Does it ensure my code executes?

No, this code is for sampling, not for scheduling. Put your code in a place where it will be call frequently. requestAnimationFrame and setInterval are good places to start.

Authors

License

MIT