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

repoll

v1.0.2

Published

Simple decorator to trigger component functions on intervals

Downloads

11

Readme

repoll

Automate polling in your React components

Table of contents

Installation

$ npm i repoll --save

Usage

import React, {
  Component
} from 'react';

import repoll from 'repoll';

@repoll({foo: 5000})
class PollingFoo extends Component {
  state = {
    counter: 0
  };
  
  foo = () => {
    this.setState({
      counter: this.state.counter + 1
    });
  };

  render() {
    <div>
      I will increment the counter every 5 seconds. The current value is {this.counter}.
    </div>
  }
}

In the above example, the foo function will be called every 5 seconds starting when the component's constructor function is fired. This is the most basic usage, but there are multiple ways you can tweak how the intervals are managed.

Injected values

When the class is decorated, an instance value of repollIntervals is injected into the class, which houses all of the intervals applied via repoll. repollIntervals is an object whose properties are each objects themselves reflecting a specific interval:

{
  interval: Number,
  name: String,
  start: Function,
  stop: Function
}

The interval and the name are just metadata; name is the name of the function, whereas interval is the ID of the interval created internally by setInterval. The start and stop functions will respectively start and stop the polling of the function.

const pollingFunctions = {
  foo: 500
};

@repoll(pollingFunctions)
class MyComponent extends Component {
  foo = () => {
    console.log('fired');
  };
  
  render() {
    console.log(this.repollIntervals);
    // {foo: {interval: 0, name: 'foo', start: [Function], stop: [Function]}}
    
    return (
      <div>
        Stuffz
      </div>
    );
  }
}

You do should not need to make use of it unless you are applying advanced usages.

Additionally, the functions that are wired for polling will have the interval injected into it:

const pollingFunctions = {
  foo: 500
};

@repoll(pollingFunctions)
class MyComponent extends Component {
  counter = 0;

  foo = (fooInterval) => {
    if (this.counter === 3) {
      console.log('Fired thrice prior, preventing any more calls.');
      
      fooInterval.stop();
    }
    
    this.counter++;
  };
  
  render() {
    return (
      <div>
        Stuffz
      </div>
    );
  }
}

Parameters

repoll(pollingFunctions: object, options: object = {})

The decorator is a composed function that accepts up to two parameters and returns a function that extends the ReactComponent that is passed to it.

pollingFunctions

This is a simple map of functionName: intervalInMilliseconds, where each functionName reflects a function instantiated in the ReactComponent. Example:

const pollingFunctions = {
  foo: 5000,
  bar: 2000
};

@repoll(pollingFunctions)
class MyComponent extends Component {
  foo() {
    console.log('I will fire every 5 seconds.');
  }
  
  bar() {
    console.log('I will fire every 2 seconds.');
  }
  
  render() {
    return (
      <div>
        I poll ths stuffz.
      </div>
    );
  }
}

As you can see, both foo and bar line up with the named methods in the class. This means that those methods will fire at the intervalInMilliseconds assigned to them in the map. If a name is called out in the map but does not exist in the class, an error is fired.

options

An object that is passed to override certain default options. The options available are:

  • autoStart boolean, defaults to true
  • stopOnUnmount boolean, defaults to true

For example, if you want to only trigger the polling after some event:

const pollingFunctions = {
  foo: 500
};
const options = {
  autoStart: false
};

@repoll(pollingFunctions, options)
class MyComponent extends Component {
  foo = () => {
    console.log('I am fired on polling.');
  };
  
  onClickButton = () => {
    this.repollIntervals.foo.start();
  };
  
  render() {
    return (
      <button
        onClick={this.onClickButton}
        type="button"
      >
        Click me to start polling
      </button>
    );
  }
}

Or if you wanted the polling to continue even after the component unmounts:

const pollingFunctions = {
  foo: 500
};
const options = {
  stopOnUnmount: false
};

@repoll(pollingFunctions, options)
class MyComponent extends Component {
  foo = () => {
    console.log('I am fired on polling and will never stop.');
  };
  
  render() {
    return (
      <div>
        I will poll forever...
      </div>
    );
  }
}

Development

Standard stuff, clone the repo and npm i to get the dependencies. npm scripts available:

  • compile-for-publish => runs the lint and transpile scripts
  • dev => runs the webpack dev server for the playground
  • lint => runs ESLint against files in the src folder
  • prepublish => if in publish, runs compile-for-publish
  • test => runs AVA with NODE_ENV=test
  • test:watch => runs test but with persistent watcher
  • transpile => runs Babel against files in src to files in lib