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

269
Views
NodeJS - Should we return instead of await to improve performance

When taking this eslint rule into consideration it looks like this kind of code should be avoided (even though the rule allows it when it is not "return await")

async function foo() {
    await bar(); // "cost of an extra microtask before resolving the outer Promise"
} // void return

And changed to

async function foo() {
    return bar(); //This may be confusing because there is no real return value
} 

So the question is - is this "extra microtask" really that significant?

Obviously when looking on 1 function - the effects are negligible, but what if it happens a lot all over the codebase?

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!