hyperquest
isomorphic-fetch
hyperquest | isomorphic-fetch | |
---|---|---|
- | 9 | |
712 | 6,961 | |
- | - | |
0.0 | 0.0 | |
about 6 years ago | about 1 year ago | |
JavaScript | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hyperquest
We haven't tracked posts mentioning hyperquest yet.
Tracking mentions began in Dec 2020.
isomorphic-fetch
-
Storyblok/Svelte v3.0.0. is here 🎉
This new version uses the latest version of our js-client - which means we are finally removing Axios in favor of native Fetch API (polyfillable via isomorphic-fetch).
-
Use fetch instead of ajax with redux-observable
In redux-observable is it possible to use isomporphic-fetch instead of Rx.DOM.ajax?
-
Storyblok Nuxt 3 news 🗞
The SDK now uses the Fetch API under the hood. If your environment doesn't support it, install a polyfill like isomorphic-fetch. More information can be found on the storyblok-js-client README.
-
Storyblok Gatsby SDK is free from axios✨
You don't need to install extra isomorphic-fetch into your Storyblok & Gatsby applications.
-
Stop polyfilling fetch in your npm package
You can get around some of the above issues using a library called isomorphic-fetch, but not all of them. It also hasn’t been updated since 2015, and is locked on v2.x of node-fetch (whereas v3 has been out for some time now)
-
fetch patch request is not allowed
I have been happily using isomorphic-fetch till I needed to send PATCH method to the server.
-
React server-side fetch (asynchronous rendering)
import React from 'react';export default class RemoteText extends React.PureComponent { constructor(props) { super(props); this.state = {text: null}; fetch(props.src).then(res => res.text()).then(text => { this.setState({text}); }) } render() { if(this.state.text) { return {this.state.text}; } return null; }} Even if I use isomorphic-fetch, I get this warning:
- What is the difference between isomorphic-fetch and fetch?
-
Centralized/modularized Axios implementation?
Not to play devil's advocate or anything, but in all fairness, fetch can use an AbortController to be cancellable. Also, it/they can easily be supported in older browsers through a polyfill, which is substantially lighter on bundle size than Axios, esp for newer browsers where the polyfills adds no new code. Short digression: I love isomorphic-fetch because it polyfills fetch in both old browsers and NodeJS, meaning I only need to remember one simple API (fetch) for network calls regardless of the environment. I'd much rather have to learn only one stable, native API than add on additional third party APIs that can change over time or require additional plugins to make it work (e.g. moxios).
What are some alternatives?
request - 🏊🏾 Simplified HTTP request client.
axios - Promise based HTTP client for the browser and node.js
node-fetch - A light-weight module that brings the Fetch API to Node.js
spdy - SPDY server on Node.js
http-proxy - A full-featured http proxy for node.js
flashheart - A fully-featured Node.js REST client built for ease-of-use and resilience
superagent - Ajax for Node.js and browsers (JS HTTP client). Maintained for @forwardemail, @ladjs, @spamscanner, @breejs, @cabinjs, and @lassjs.
Nock - HTTP server mocking and expectations library for Node.js
http-fake-backend - Build a fake backend by providing the content of JSON files or JavaScript objects through configurable routes.