Simple and extensible HTTP client library built on top of fetch with caching and retry. Works on browser, Node.js, Bun, and more.
An uncomplicated and extensible HTTP client library built on top of fetch, equipped with caching and retry mechanisms. Suitable for the browser, Node.js, Bun, and more.
ReqMate wraps fetch to simplify its use and add commonly required capabilities. It employs the builder pattern to create and send requests. The basic way to use it is to call reqmate, specify the HTTP verb, and then call send. Here's a code snippet to demonstrate:
// Import the lib
import reqmate from 'reqmate';
// GET
const getRequest = await reqmate.get("/product?id=666").send();
// POST
const postBody = {name : "The Necronomicon", type : "book", price : 11}
const postRequest = await reqmate.post("/product", postBody).send();
// PUT
const putBody = {id : 666, name : "The Necronomicon", type : "book", price : 11};
const putRequest = await reqmate.put("/product", putBody).send();
// PATCH
const patchBody = {id : 666, price : 666};
const patchRequest = await reqmate.patch("/product", patchBody).send();
// DELETE
const deleteRequest = await reqmate.delete("/product/666").send();
// Basic example with caching and polling
const response = await reqmate
.get('https://jsonplaceholder.typicode.com/todos/3')
.setCache(30000) // Cache will store for 30 seconds
.setRetry({
type: 'polling',
maxRetries: 3,
onResponse: (response, done) => console.log({response}),
})
.send();
Fields such as mode, credentials, cache, and redirect can be specified by setting the request's config. Here's a sample:
const getRequest = await reqmate
.get("/product?id=666")
.setConfig({
mode : "cors",
credentials : "include",
cache : "no-cache",
redirect : "follow"
})
.send();
The response object comprises:
ok field).{
"ok":true,
"status":200,
"headers":{
"cache-control":"max-age=43200",
"content-type":"application/json; charset=utf-8",
"expires":"-1",
"pragma":"no-cache"
},
"cached":false,
"data":{
"userId": 1,
"id": 1,
"title": "delectus aut autem",
"completed": false
}
}
The parser is a promise that processes the raw request response. By default, ReqMate utilizes parsers based on the Content-Type header value. Most use cases won't require an override. However, if needed, a custom parser can replace the default by using the setParser step of the builder. Here's an example using a custom parser:
const isPostSuccess : Boolean = await reqmate
.post(URL, { payload: "hello" })
.setParser(response => response.status === 201)
.send();
// isPostSuccess will be a boolean, if the response status is 201 will be set to true
// Another example, will process the response and return the processed value on the data field. (You can try this one on you own code)
const { data } = await reqmate
.get("https://jsonplaceholder.typicode.com/todos/1")
.setParser(async (response: Response) => {
const { title, completed } = await response.json();
return `${title} is ${completed ? "Completed" : "Not Completed"}`;
})
.send<string>();
// data will be the string "delectus aut autem is Not Completed" instead of the full object returned by the server
// Taking it further, on the following react example, we are gonna return a component directly.
// This will return a text that will be green or red depending on the completed field
import reqmate from 'reqmate';
import { useState, useEffect } from 'react';
function App(){
const [todo, setTodo] = useState<React.FC | undefined>(undefined);
async function loadTodo() {
const { data } = await reqmate
.get("https://jsonplaceholder.typicode.com/todos/1")
.setParser(async (response: Response) => {
const { title, completed } = await response.json();
const color = completed ? 'green' : 'red';
return <p style={{ color }}>{title}</p>;
})
.send<React.FC>();
setTodo(data);
}
return (
<>
{todo}
<button onClick={loadTodo}>Load Todo</button>
</>
)
}
With ReqMate, you can cache your HTTP calls. Simply invoke the setCaching step of the builder. If setCaching is called without parameters, the request is cached indefinitely. However, a time-to-live (TTL) can be specified in milliseconds to determine cache expiration.
// Will cache the entire response forever
const responseCachedForever = await reqmate
.get('https://jsonplaceholder.typicode.com/todos')
.setCaching()
.send();
// Will cache the result for 3 seconds
const response = await reqmate
.get('https://jsonplaceholder.typicode.com/todos/1')
.setCaching(3000)
.send();
// Cached response will resolve automatically because the value is still on the cache
const cachedResponse = await reqmate
.get('https://jsonplaceholder.typicode.com/todos/1')
.send();
ReqMate offers two retry strategies: Polling and Timed. You can customize these strategies for different requirements.
To handle each response, you can provide a callback to the onResponse property. This callback receives two arguments: the parsed response and a done() function. Invoking done() will halt the retry process and resolve the promise with the last received value. Similarly, onError can be used to handle request failures.
Polling initiates a new request after the completion (whether successful or failed) of the previous one. It continues until the maxRetries count is reached or the done() function is called. Below is an example:
const response = await reqmate
.get('https://jsonplaceholder.typicode.com/todos/3')
.setRetry({
type: 'polling',
maxRetries: 3,
onResponse: (r, done) => {
console.log('RESPONSE: ', r)
if(r.data.id === 3) {
done();
}
},
onError : (err, done) => {
console.error(err);
done();
}
})
.send();
The Timed strategy triggers a new request based on specified intervals, providing flexibility with various sub-strategies:
Example of Exponential Backoff:
The doExponentialBackoff function receives the parameters:
Example: if interval is 1000 miliseconds, the second call will be made at 2000 , the third one at 4000 etc.. (8k, 16k, 32k ...)
import reqmate, { Timed } from 'reqmate';
function doExponentialBackoff() {
reqmate
.get('https://jsonplaceholder.typicode.com/todos/3')
.setRetry({
type: 'timed',
interval: 1000,
maxRetries: 30, // 30 retries
timeout: 10000, // 10 seconds
intervalCallback: Timed.doExponentialBackoff(2, 100000),
onResponse: (r) => console.log('RESPONSE: ', r),
onError: (e) => console.log('ERROR: ', e)
})
.send()
.then((res) => console.log('RES: ', res));
}
Example of Exponential Linear:
The doLinearBackoff function receives the parameters:
Example: if interval is 1000 milliseconds and factor is 200, the next call will be made at 1200, the third one at 1400 etc..
import reqmate, { Timed } from 'reqmate';
function doLinearBackoff() {
reqmate
.get('https://jsonplaceholder.typicode.com/todos/3')
.setRetry({
type: 'timed',
maxRetries: 30, // 30 retries
timeout: 10000, // 10 seconds
intervalCallback: Timed.doLinearBackoff(200, 1000),
onResponse: (r) => console.log('RESPONSE: ', r),
onError: (e) => console.log('ERROR: ', e)
})
.send()
.then((res) => console.log('RES: ', res));
}
Example of Static Backoff (default strategy)
The
doStaticBackofffunction, does not receives any parameters. All calls will be made with the specified interval.
function doStaticBackoff() {
reqmate
.get('https://jsonplaceholder.typicode.com/todos/3')
.setRetry({
type: 'timed',
interval: 1000,
maxRetries: 30, // 30 retries
timeout: 10000, // 10 seconds
intervalCallback: Timed.doStaticBackoff(),
onResponse: (r) => console.log('RESPONSE: ', r),
onError: (e) => console.log('ERROR: ', e)
})
.send()
.then((res) => console.log('RES: ', res));
}
Example of Random backoff
The doRandomBackoff receives the parameters
Example if called with the parameters 1000 and 5000 all calls will be made with a random interval betwee these two values each time.
function doRandomBackoff() {
reqmate
.get('https://jsonplaceholder.typicode.com/todos/3')
.setRetry({
type: 'timed',
maxRetries: 30, // 30 retries
timeout: 10000, // 10 seconds
intervalCallback: Timed.doRandomBackoff(1000, 5000),
onResponse: (r) => console.log('RESPONSE: ', r),
onError: (e) => console.log('ERROR: ', e)
})
.send()
.then((res) => console.log('RES: ', res));
}
You're not limited to the built-in strategies. ReqMate allows you to define custom strategies using the intervalCallback.
The intervalCallback is just a high order function that returns a function that return the interval.
Example of a custom made retry mechanism, this retry will alternate between 1 and 3 seconds for the intervals.
function doCustomBackoff() {
function customRetry() {
let isFlagTrue = true;
return () => {
isFlagTrue = !isFlagTrue;
console.log('isFlagTrue: ', isFlagTrue);
return isFlagTrue ? 1000 : 3000;
}
}
reqmate
.get('https://jsonplaceholder.typicode.com/todos/3')
.setRetry({
type: 'timed',
maxRetries: 30, // 30 retries
timeout: 10000, // 10 seconds
intervalCallback: customRetry(),
onResponse: (r) => console.log('RESPONSE: ', r),
onError: (e) => console.log('ERROR: ', e)
})
.send()
.then((res) => console.log('RES: ', res));
}
By default, ReqMate provides an in-memory cache. However, you can replace this with a custom implementation. Your custom cache should adhere to the ReqMateCache interface:
export default interface ReqMateCache {
has(key: string): Promise<boolean>;
set(key: string, value: unknown, ttl?: number): Promise<void>;
get(key: string): Promise<unknown>;
delete(key: string): Promise<boolean>;
expire(key: string, ttl: number): void;
clear(): Promise<void>;
size(): Promise<number>;
keys(): Promise<IterableIterator<string>>;
values(): Promise<IterableIterator<unknown>>;
entries(): Promise<IterableIterator<[string, unknown]>>;
forEach(callbackfn: (value: unknown, key: string, map: Map<string, unknown>) => void, thisArg?: unknown): Promise<void>;
generateKey(data: unknown): Promise<string>;
}
To demonstrate, here's an example that employs localStorage for caching (this class is just an example):
import reqmate from 'reqmate';
import ReqMateCache from 'reqmate/cache/ReqMateCache'
export default class LocalStorageCache implements ReqMateCache {
constructor(public prefix: string = 'ReqMateCache_') { }
private async getRaw(key: string): Promise<{ value: unknown, expiration?: number }> {
const data = localStorage.getItem(this.prefix + key);
return data ? JSON.parse(data) : null;
}
async has(key: string): Promise<boolean> {
const raw = await this.getRaw(key);
if (raw && (!raw.expiration || raw.expiration > Date.now())) {
return true;
}
return false;
}
async set(key: string, value: unknown, ttl?: number): Promise<void> {
const item = {
value,
expiration: ttl ? Date.now() + ttl * 1000 : undefined,
};
localStorage.setItem(this.prefix + key, JSON.stringify(item));
}
async get(key: string): Promise<unknown> {
const raw = await this.getRaw(key);
if (raw && (!raw.expiration || raw.expiration > Date.now())) {
return raw.value;
}
return null;
}
async delete(key: string): Promise<boolean> {
if (await this.has(key)) {
localStorage.removeItem(this.prefix + key);
return true;
}
return false;
}
expire(key: string, ttl: number): void {
this.getRaw(key).then(raw => {
if (raw) {
raw.expiration = Date.now() + ttl * 1000;
localStorage.setItem(this.prefix + key, JSON.stringify(raw));
}
});
}
async clear(): Promise<void> {
Object.keys(localStorage).forEach(k => {
if (k.startsWith(this.prefix)) {
localStorage.removeItem(k);
}
});
}
async size(): Promise<number> {
return Object.keys(localStorage).filter(k => k.startsWith(this.prefix)).length;
}
async keys(): Promise<IterableIterator<string>> {
const keys = Object.keys(localStorage).filter(k => k.startsWith(this.prefix)).map(k => k.substr(this.prefix.length));
return keys[Symbol.iterator]();
}
async values(): Promise<IterableIterator<unknown>> {
const rawKeys = await this.keys();
const keys = [...rawKeys];
const values = keys.map(k => this.get(k));
return values[Symbol.iterator]();
}
async entries(): Promise<IterableIterator<[string, unknown]>> {
const rawkeys = await this.keys();
const keys = [...rawkeys];
const entries = keys.map(k => [k, this.get(k)] as [string, unknown]);
return entries[Symbol.iterator]();
}
async forEach(callbackfn: (value: unknown, key: string, map: Map<string, unknown>) => void, thisArg?: unknown): Promise<void> {
const map = new Map<string, unknown>();
const entries = await this.entries();
for (const [key, value] of entries) {
map.set(key, value);
}
map.forEach(callbackfn, thisArg);
}
async generateKey(target: Object): Promise<string> {
const str = JSON.stringify(target, Object.keys(target).sort());
let hash = 0;
for (let i = 0; i < str.length; i++) {
const char = str.charCodeAt(i);
hash = ((hash << 5) - hash) + char;
hash = hash & hash;
}
return hash.toString();
}
}
To set your custom cache in ReqMate:
// Set the newly implemented cache as the cache for reqmate.
reqmate.cache = new LocalStorageCache("app_");
const r = await reqmate
.get('https://jsonplaceholder.typicode.com/todos/1')
.setCaching(500000)
.setRetry({
type: 'timed',
maxRetries: 3,
interval: 1000,
onResponse: (r) => console.log('RESPONSE: ', r),
intervalCallback: Timed.doExponentialBackoff()
})
.send();
console.log("HAS: ", await reqmate.cache.has(r.cacheKey!));
console.log("GET:", await reqmate.cache.get(r.cacheKey!));
Similarly, you can retrieve the cache from ReqMate:
const cache = reqmate.cache;
console.log(await cache.size())
// or calling it directly
console.log(await reqmate.cache.size())
Retry mechanisms can be created using the RetryFactory or by directly instantiating specific retry classes. These mechanisms can also be repurposed for other promises.
Here's how you can create a Polling-type Retry object using the Factory:
import {RetryFactory} from 'reqmate';
const retry = RetryFactory.build({
type: 'polling',
maxRetries: 3,
onResponse: (r, done) => console.log('RESPONSE: ', r),
onError : (err, done) => console.error(err),
});
Both Polling and Timed classes can be instantiated directly. You can then inject them using the setRetry. Here are examples for both:
async function doPolling() {
// Doing one chain.
const polling = (new Polling())
.onResponse((r) => console.log('RESPONSE: ', r))
.onError((e) => console.log('ERROR: ', e))
.setMaxRetries(3);
const { data } = await reqmate
.get("https://jsonplaceholder.typicode.com/todos/1")
.setRetry(polling)
.send<Record<string, string>>();
console.log({ data })
}
async function doTimed() {
// Instantiating the class
const timed = new Timed();
// Adding the steps.
timed.onResponse((r) => console.log('RESPONSE: ', r))
.onError((e) => console.log('ERROR: ', e))
.setMaxRetries(3)
.setInterval(1000)
.setTimeout(10000)
.setIntervalCallback(Timed.doExponentialBackoff());
const { data } = await reqmate
.get("https://jsonplaceholder.typicode.com/todos/1")
.setRetry(timed)
.send<Record<string, string>>();
console.log({ data })
}
The retries mechanisms can be used as an standalone utility to execute promises using these strategies. The keys for this are two other methods:
setCallback : Sets the callback to be executed, this callback is expected to return a promise.execute: Will trigger the execution.On the example bellow, we are reading information from a file and the process will stop when the value from the file is the string value '3'. On the other hand, we are writing into the file a counter that will increase every second, so the reading will stop when the writing puts the value '3' into the file.
const fs = require('fs').promises;
const { Polling, Timed } = require('reqmate');
// Test promise for reading a file
async function readFile(filePath) {
try {
const data = await fs.readFile(filePath, 'utf8');
return data;
} catch (error) {
throw new Error(`Could not read the file: ${error.message}`);
}
}
// Test promise for writing into a file
async function writeFile(filePath, data) {
try {
await fs.writeFile(filePath, data, 'utf8');
console.log('Data successfully written to file.');
} catch (error) {
throw new Error(`Could not write to the file: ${error.message}`);
}
}
async function readTimed() {
// Will do a Polling on readFile until the value of the file is '3'.
(new Polling())
.setCallback(() => readFile('file.txt'))
.onResponse((r, done) => {
console.log("READING: ", r)
if (r === "3") done();
})
.execute();
}
async function writeTimed() {
// Will write the counter into the file with 1 second interval
let counter = 0;
const timed = new Timed();
timed.setInterval(1000)
.setTimeout(5000)
.setCallback(() => {
counter++;
writeFile('file.txt', `${counter}`)
})
.execute();
}
readTimed();
writeTimed();
FAQs
Simple and extensible HTTP client library built on top of fetch with caching and retry. Works on browser, Node.js, Bun, and more.
We found that reqmate demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.