plugin-throttling.js

> Octokit plugin for GitHub’s recommended request throttling


Implements all recommended best practices to prevent hitting secondary rate limits.

Usage

Browsers	Load @octokit/plugin-throttling and @octokit/core (or core-compatible module) directly from esm.sh ``html `
Node	Install with npm install @octokit/core @octokit/plugin-throttling. Optionally replace @octokit/core with a core-compatible module. `js import { Octokit } from "@octokit/core"; import { throttling } from "@octokit/plugin-throttling"; `

> [!IMPORTANT]
> As we use conditional exports, you will need to adapt your tsconfig.json by setting "moduleResolution": "node16", "module": "node16".
>
> See the TypeScript docs on package.json "exports".

> See this helpful guide on transitioning to ESM from @sindresorhus

The code below creates a "Hello, world!" issue on every repository in a given organization. Without the throttling plugin it would send many requests in parallel and would hit rate limits very quickly. But the @octokit/plugin-throttling slows down your requests according to the official guidelines, so you don't get blocked before your quota is exhausted.

The throttle.onSecondaryRateLimit and throttle.onRateLimit options are required. Return true to automatically retry the request after retryAfter seconds.

`js
const MyOctokit = Octokit.plugin(throttling);

const octokit = new MyOctokit({
auth: secret123,
throttle: {
onRateLimit: (retryAfter, options, octokit, retryCount) => {
octokit.log.warn(
Request quota exhausted for request ${options.method} ${options.url},
);

if (retryCount < 1) {
// only retries once
octokit.log.info(Retrying after ${retryAfter} seconds!);
return true;
}
},
onSecondaryRateLimit: (retryAfter, options, octokit) => {
// does not retry, only logs a warning
octokit.log.warn(
SecondaryRateLimit detected for request ${options.method} ${options.url},
);
},
},
});

async function createIssueOnAllRepos(org) {
const repos = await octokit.paginate(
octokit.repos.listForOrg.endpoint({ org }),
);
return Promise.all(
repos.map(({ name }) =>
octokit.issues.create({
owner,
repo: name,
title: "Hello, world!",
}),
),
);
}
`

Pass { throttle: { enabled: false } } to disable this plugin.

$3

Enabling Clustering support ensures that your application will not go over rate limits across Octokit instances and across Nodejs processes.

First install either redis or ioredis:

`


NodeRedis (https://github.com/NodeRedis/node_redis)

npm install --save redis

or ioredis (https://github.com/luin/ioredis)

npm install --save ioredis
`

Then in your application:

`js
import Bottleneck from "bottleneck";
import Redis from "redis";

const client = Redis.createClient({
/ options /
});
const connection = new Bottleneck.RedisConnection({ client });
connection.on("error", err => console.error(err));

const octokit = new MyOctokit({
auth: 'secret123'
throttle: {
onSecondaryRateLimit: (retryAfter, options, octokit) => {
/ ... /
},
onRateLimit: (retryAfter, options, octokit) => {
/ ... /
},

// The Bottleneck connection object
connection,

// A "throttling ID". All octokit instances with the same ID
// using the same Redis server will share the throttling.
id: "my-super-app",

// Otherwise the plugin uses a lighter version of Bottleneck without Redis support
Bottleneck
}
});

// To close the connection and allow your application to exit cleanly:
await connection.disconnect();
`

To use the ioredis library instead:

`js
import Redis from "ioredis";
const client = new Redis({
/ options /
});
const connection = new Bottleneck.IORedisConnection({ client });
connection.on("error", (err) => console.error(err));
`

Options






































name	type	description
options.retryAfterBaseValue	Number	Number of milliseconds that will be used to multiply the time to wait based on retry-after or x-ratelimit-reset headers. Defaults to 1000
options.fallbackSecondaryRateRetryAfter	Number	Number of seconds to wait until retrying a request in case a secondary rate limit is hit and no retry-after header was present in the response. Defaults to 60
options.connection	Bottleneck.RedisConnection	A Bottleneck connection instance. See Clustering above.
options.id	string	A "throttling ID". All octokit instances with the same ID using the same Redis server will share the throttling. See Clustering above. Defaults to no-id.
options.Bottleneck	Bottleneck	Bottleneck constructor. See Clustering above. Defaults to bottleneck/light`.

LICENSE

MIT