Async JavaScript Callback Functions, Error Handling and Callback Hell

In this video we are going to learn about what are Callback Functions in JavaScript and we use them for performing Async tasks as Callback themselves are not Async by default. We will also see what is the good way to handle errors in Callback and what is Callback hell ?

***Watch this video to understand better***

***Checkout my crash courses for get started with web development***

🔗 Social Medias 🔗

⭐️ Tags ⭐️
- Async Programming JavaScript
- JavaScript Synchronous
- Callbacks
- Callback Hell Nodejs
- Nodejs Callback

⭐️ Hashtags ⭐️
#Synchronous #Async #Tutorials

Disclaimer:
It doesn't feel good to have a disclaimer in every video but this is how the world is right now.
All videos are for educational purpose and use them wisely. Any video may have a slight mistake, please take decisions based on your research. This video is not forcing anything on you.

[jampalachandana]

At 3:50 you got reference error because ‘name’ is hoisted but not initialised.If you call asyncTask after initialisation of name, the error will be resolved no need to use setTimeout.

[mocococo]

Thank you and greetings from Bulgaria.
Please explain why in your first example you called the callback function directly:
- here there is only one f-n, no intermedite function inside the brackets.

In you last example however you use anonymous intermediate functions ??

asyncTask(()=>{ - here those functions I mean
asyncTask(()=>{ - here those functions I mean


You could call asyncTask() directly without that. For ex.

asyncTask(
asyncTask(


Thank you.

[contentshark]

We can avoid nesting by writing settimeout...where it will be a nonblocking aych approch...then why do we have to write async in sequetial manner... ?