Search for a command to run...
No comments yet. Be the first to comment.
A quick analysis of the top 25 CWEs in the last 5 years show a repeating pattern
JavaScript is a scripting language, therefore you can write scripts to automate your workflow with JavaScript. The background of the snippet I created a node script recently to automate one workflow that I do repeatedly. Every time I create a new Jav...
In this article, you will learn to build a Markdown parser which compiles into HTML with JavaScript and Regular Expression Markdown is a markup language like HTML. It is quite popular among developers to write blogs, readme files, and documentation. ...
Handling error in express applications can be more challenging than building web applications and APIs Building web applications or APIs with express.js is not difficult in my opinion. I think it is more difficult to handle errors, error status codes...
This blog is a follow-up to my last blog in which I talked about promises. If you are unfamiliar with promises in JavaScript, please read that article before reading this one. Also, some familiarity with exception handling would be useful. Async Awai...
Error handling is vital while making AJAX requests in any tool. The solution I propose can be applicable for all kinds of frameworks or libraries. I am used to working with React.JS and in this blog, I talk about the approach I use handling errors that occur during AJAX requests.
There can be 3 kinds of situation where we might receive errors.
This kind of error might occur if there's no internet connection or the server is not running.
This kind of error might occur in the following scenarios.
We have a server that authenticates the users. We send username and password to the server and the password is incorrect. In this case, we have sent the data, the server has recieved the data but the information we're sending with the request is invalid.
This is the easiest way to handle error because we on the front end (or the side to send request), don't have to think what might have gone wrong. If the API is built considering the errors, it will respond with proper error message.
Axios automatically throws errors that lie out of the range 2xx and the kinds of error I have mentioned above returns a status code that falls out this range.
I have never faced error of this kind while building application but there might be something that might go wrong. We don't know what it is but there might be something. In this case, we could consider handling these kinds of errors.
Below, I define a function that makes an AJAX request to a dummy API and handle the errors I've mentioned above.
const makeRequest = async () => {
try {
const response = await axios.get("https://somedummyapi.com")
return response
} catch (error) {
if (error.request) {
// Maybe we don't have internet connection
// or our server has stopped
console.log("Could not connect to the server")
} else if (error.response) {
// Server received a request
// and responded with a status code
// that falls out of the range 2xx.
console.log(error.response.data)
} else {
// something happened while making the request
// that we're not really aware of
console.log(error)
}
}
}
These are the most common types of error I try to handle while building JavaScript Apps with React and I think you should too. 😄