This will soon no longer be considered valid JavaScript:

import * as useFetch from 'fetch-suspense'

useFetch(/*...*/)

https://stackoverflow.com/questions/39415661/what-does-resolves-to-a-non-module-entity-and-cannot-be-imported-using-this/39415662#39415662

An ES6 module namespace object cannot be invoked as a function or with new.
The thing you import using * as X from a module is defined to only have properties.

As a backwards-compatible change, this module should have something like this added to the bottom of fetch-suspense.ts:

module.exports.useFetch = module.exports

That way we'll be able to do this:

import { useFetch } from 'fetch-suspense'

useFetch(/*...*/)

Hi, great library! I am testing the metadata parameter, because I expected the hook to throw when receiving a non-200 status code. However, I always get this metadata:

Object {
  "bodyUsed": undefined,
  "contentType": "text/html; charset=utf-8",
  "headers": undefined,
  "ok": undefined,
  "redirected": undefined,
  "response": "...",
  "status": undefined,
  "statusText": undefined,
  "url": undefined,
}

The same request in Postman gives the following status:

Is this a bug, or am I doing something wrong and is it working as designed?

First of all I'd like to thank your for this awesome package.

But now for a feature request / question.

What if I have a component that needs to do multiple fetch requests before rendering? How would you extend this hook to be able to handle multiple fetch requests?

Hi @CharlesStover! First off thanks for writing this package.

The only thing that I noticed was that maxDuration seems to not be respected and the loading spinner seems to show right away. Have you experienced this at all?

More specifically, this is a complaint that happens:

import useFetch from 'fetch-suspense';
//                    ~~~~~~~~~~~~~~~~
// File '/Users/user/repos/Project/node_modules/fetch-suspense/fetch-suspense.d.ts' is not a module.ts(2306)

fetch-suspense.d.ts should export useFetch to indicate that it's exported. Right now, it's implying there's a global const useFetch variable.

Hello!

Thanks for this great library. It's been super helpful and works well.

I'm wondering if its going to be possible ever to trigger a manual cache clear. Say we are loading a user profile on page load. That data doesn't change often, and can be cached. If a user updates their profile though, we will need the ability to clear the cached response in order to trigger a refetch.

Hope this makes sense as a use case, and thanks again!

Hello,

I can't figure out how to handle fetch errors with fetch-suspense.
I'd like to show an error message to the user if something fails.
Could you provide an example, possibly with some comments on it?

Thank you!

Please consider also building a UMD/standalone version.

You can read about the AbortController here: https://developer.mozilla.org/en-US/docs/Web/API/AbortController

fetch-suspense is designed to work with React concurrent mode's Suspense. The fetch-suspense README contains an excellent example of usage with Suspense.

The other main new API in concurrent mode is useTransition. It would be helpful to have a README example showing to use fetch-suspense within a startTransition created by useTransition.

Similar issue: apollographql/apollo-link#1131

Wamp wump. I can fix this too. 😅

If I go offline, fetch throws and the whole application goes to hell. fetch-suspense should catch the error and return it so it can be handled properly.