npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@dreamworld/fetch

v2.0.3

Published

It's fetch, which auto retry on failure

Downloads

164

Readme

Fetch API with retryable

  • When http response isn't received (status code = 0), request is always & infinitely retried.
  • When http response is other than 5xx, request is never retried.

Retry

It automatically performs retry on various common errors. e.g.

  • Network Error
  • 503: Service Unavailable

All 4xx errors are considered client errors, and they are NEVER retried.

Don't retry 5xx except 503

Earlier we were performing retry on 500 errors too. But, all retries were failing with the same error. So, it was simply generating load (and errors) on the server; and not helping user. As an inverse effect, user need to wait for few seconds to see error.

So, we planned to not retry any of the 500 error.

Similarly, another common error is 504 - Gateway Timeout. This can happen when a service takes longer than 1 minute to respond. And any intermediate proxy (nginx or api-gateway) considers it as timeout and responds with 504. This error is not common, and most often suggests a change in the API design. If API is suppose to take longer to process; then it should respond with 201 - Accepted. And provide an companion API to read the status of the request. Additionally, retrying in this case can cause duplicate records on teh server (if it was write API). So, 504 error should also not be retried ever.

But, "503 - Service Unavailable" could be a temporary error. And if retry is performed for next 1-2 minute it should succeed once. As all microservices are deployed with high-availability setup, this error is also not expected ever. But, in rare case if it happens, it should be retried.

Override default behaviour

User can specify explicitly whether a request is retryable or not through options { retryable: true }; whenever options are specified, it's considered and default behaviour is ignored.

Usage pattern

import fetch from '@dreamworld/fetch';

Get Pending write / read requests

// store.js
import { initRedux as initFetchRequestRedux } from '@dreamworld/fetch';
initFetchRequestRedux(store);

// Get Pending writes / reads.
import * as fetchSelectors from '@dreamworld/fetch/selectors.js';

fetchSelectors.pendingWrites(state); // { 5AqmtnIKAReGLCeUFcvj5b: 1689319833142, ... }

fetchSelectors.pendingReads(state); // { 9BqmtnIKAReGLCeUFcvj5b: 1689319833142, ... }