How to deal with errors? Not presenting error information. about axios-hooks HOT 8 CLOSED

You will find all this information in the error property, or am I missing something?

const [{ error }] = useAxios(...)

from axios-hooks.

Strange, it's not giving me an object, it's giving me this instead:

Error: Network Error
    at createError (createError.js:16)
    at XMLHttpRequest.handleError (xhr.js:81)

Going to try and reproduce it in codesandbox, I'll update this comment afterwards.

from axios-hooks.

okay sure. that object though is what's returned by axios, see

from axios-hooks.

I coudn't reproduce my problem, but I noticed that it's something that is documented in axios.

At least I know where the problem lies. Basically the error occurred on the request, so error.response is obviously still undefined. I could identify this by checking all the values mentioned in axios' docs.

error.response -->  undefined
error.request -->  XMLHttpRequest {klIsCORSRequest: true, readyState: 4, timeout: 0, withCredentials: false, onreadystatechange: ƒ, …}
error.message -->  Network Error
error.config -->  {url: "https://nonexistingurl.com", method: "get", headers: {…}, transformRequest: Array(1), transformResponse: Array(1), …}

from axios-hooks.

Correct, though unusual, HTTP errors may occur on the request rather than in the response (i.e. there's no network connectivity so the request cannot even leave the local network). In those cases, you will never have a response and in Axios that's communicated by an undefined response on the error object.

from axios-hooks.

@simoneb I think this is more like react issue, but anyway.

I had almost the same problem -- I request a wrong URL, which does not exist, then axios literally died and my NextJS server also died.

logs:

client/node_modules/axios/lib/core/createError.js:16
  var error = new Error(message);
              ^

Error: Request failed with status code 404 at createError (client/node_modules/axios/lib/core/createError.js:16:15)

// really long (2200) config, request, response object info

error Command failed with exit code 1.

I don't think this is normal behavior. Axios dosen't return error, just die with react.

from axios-hooks.

This is a bug in your code. Neither axios or react simply "die".

from axios-hooks.

@simoneb Thank you for reply. It was actually ssr issue. when I set option {ssr: false} that problem was gone.

I think nextJS or some of my unconscious setup make axios do a job at server-side.

from axios-hooks.