A simple response handler which rejects fetch requests on any non-2xx response.
minimal implementation of a PassThrough stream
Provides a way to make requests
An implementation of window.fetch in Node.js using Minipass streams
A light-weight module that brings Fetch API to node.js
Opinionated, caching, retrying fetch client
Kiota request adapter implementation with fetch
Blob & File implementation in Node.js, originally from node-fetch.
Decorator for a `fetch` function to support automatic cookies.
Cross Platform Smart Fetch Ponyfill
A well-tested CSS minifier
Implementation of window.fetch which can use http2 seamlessly
better fetch for Node.js. Works on any JavaScript runtime!
Property based testing framework for JavaScript (like QuickCheck)
HTTP/1+2 Fetch API client for Node.js
A window.fetch polyfill.
Streaming http in the browser
Extend any fetch library with retry functionality
Isomorphic WHATWG Fetch API, for Node & Browserify
Tiny and elegant HTTP client based on the Fetch API
A light-weight module that brings Fetch API to node.js
Switches between unfetch & node-fetch for client & server.
fetch mock for vitest
A light-weight module that brings window.fetch to node.js
[](http://travis-ci.org/estately/rets) A pure-ruby library for fetching data from [RETS] servers. If you're looking for a slick CLI interface check out [retscli](https://github.com/summera/retscli), which is an awesome tool for exploring metadata or learning about RETS. [RETS]: http://www.rets.org
[](http://travis-ci.org/estately/rets) A pure-ruby library for fetching data from [RETS] servers. If you're looking for a slick CLI interface check out [retscli](https://github.com/summera/retscli), which is an awesome tool for exploring metadata or learning about RETS. [RETS]: http://www.rets.org
Provides an SCM agnostic way to manage subprojects with a workflow similar to the scm:externals feature of subversion. It's particularly useful for rails projects that have some plugins managed by svn and some managed by git. For example, "ext install git://github.com/rails/rails.git" from within a rails application directory will realize that this belongs in the vendor/rails folder. It will also realize that this URL is a git repository and clone it into that folder. It will also add the vendor/rails folder to the ignore feature for the SCM of the main project. Let's say that the main project is being managed by subversion. In that case it adds "rails" to the svn:ignore property of the vendor folder. It also adds the URL to the .externals file so that when this project is checked out via "ext checkout" it knows where to fetch the subprojects. There are several other useful commands, such as init, touch_emptydirs, add_all, export, status. There's a tutorial at http://nopugs.com/ext-tutorial The reason I made this project is that I was frustrated by two things: 1. In my opinion, the workflow for svn:externals is far superior to git-submodule. 2. Even if git-submodule was as useful as svn:externals, I would still like a uniform way to fetch all of the subprojects regardless of the SCM used to manage the main project.
Contentful API wrapper library exposing an ActiveRecord-like interface