Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

125
Views
Javascript debugging with parallely looking into the message queue

I have learnt about the 'eventloop' and 'message queue' recently and now having pretty much idea about how the event loop helps to execute the methods that are queued in 'message queue' once the stack got empty. But am having one doubt here, while debugging the methods which are available in stacks in chrome browser, Is there is anyway we can identify what are the methods that are present in 'message queue' upto current debug point and which are going to execute by event loop once the current stack is empty.? Correct me if my question is wrong or my understanding is wrong because am new to these topics.

For Example:

const sayHello = () => console.log("Hello");

const sayBye = () => console.log("Bye");

setTimeout(sayBye,1000);

sayHello();

In the above example from my understanding the sayHello() will execute first and at the meantime sayBye function is kept in the message queue until the current stack got emptied which is handled by event loop. So while execution of the sayHello(), If I put a break point inside sayHello()(in Chrome browser) at that time is there is any where in the browser tools or any window we can see and visualize that sayBye is kept in 'Message Queue'?

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!