Custom class to handle api requests and responses.
An implementation of window.fetch in Node.js using Minipass streams
A light-weight module that brings Fetch API to node.js
Synchronous version of the Fetch API
Fetches the contents of a file accross node and browsers.
Advanced fetch wrapper for typescript with zod schema validations, pre-defined routes, hooks, plugins and more. Works on the browser, node (version 18+), workers, deno and bun.
Synchronous version of the Fetch API
A tiny wrapper built around fetch with an intuitive syntax.
Cross Platform Smart Fetch Ponyfill
Provides a way to make requests
Opinionated, caching, retrying fetch client
Universal WHATWG Fetch API for Node, Browsers and React Native
better fetch for Node.js. Works on any JavaScript runtime!
Fetch-based http client for use with npm registry APIs
api-fetch-wrapper
A simple common HTTP client specifically for Google APIs and services.
Vitest wrapper for fetch-mock
Isomorphic WHATWG Fetch API, for Node & Browserify
jest wrapper for fetch-mock
HTTP2 client, just with the familiar `https` API
OpenTelemetry instrumentation for `undici` http client and Node.js fetch()
Extend any fetch library with retry functionality
Blob & File implementation in Node.js, originally from node-fetch.
Fast, type-safe @tanstack/react-query client to work with your OpenAPI schema.
A tiny Fetch API wrapper that allows you to make http requests without need to handle to send the CSRF Token on every request
this is tinder api wrapper. we can fetch and post to tinder.
Simple Ruby client for Diablo 3 API
An Xbox API wrapper that allows one to fetch profiles, games, achievements and friends data
Simple wrapper to fetch info from Dispatch External IDs API
API wrapper for Google static maps. Will also fetch the image for you.
Provides a wrapper around Rest APIs to fetch the current BTC/Fiat value.
A basic Ruby wrapper for the API provided by LyricsWiki (http://lyrics.wikia.com/). Currently only implements fetching artist data, song data, and song lyrics.
A simple Ruby Wakoopa API wrapper, built to give you an ActiveRecord-like way to fetch your software usage data.
Unofficial Ruby wrapper for Flightradar24 API. Fetch real-time flight data, airport statistics, airline information, and more. For terms see: https://www.flightradar24.com/terms-and-conditions
Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.
Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. This works only on plural requests. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.