orinak / choker

Throttle on limited rate

choker

throttle on limited rate

Installation

npm install choker

Usage

const choker = require('choker')

const rate = {
  limit: 20,
  interval: 1000 // ms
}

async function sendSMS (data) {
  // perform request...
  return `Sent to ${data.to}`
}

const smsList = [
  { to: 777888, msg: 'hi' },
  // ...
]

choker(rate, sendSMS, smsList)
  .then(console.log)

// [
//   'Sent to 777888',
//   ...
// ]

Development

# clone repo
git clone https://github.com/despan/choker

#
cd choker

# install dependencies
npm install

Test

# run quick tests
npm run test

# test watching file changes
npm run test:watch

Contributing

Check Contributing Guide.

Acknowledgements

• Choker logo by Olena Panasovska from the Noun Project

License

The MIT License

choker's Issues

High resolution timers

The timestamp is not actually high-resolution. To mitigate security threats such as Spectre, browsers currently round the results to varying degrees. (Firefox started rounding to 1 millisecond in Firefox 60.) Some browsers may also slightly randomize the timestamp. The precision may improve again in future releases; browser developers are still investigating these timing attacks and how best to mitigate them.

Consider using performance.now() for browsers and process.hrtime.bigint() in Node.js.