2 ms·

You should however, catch it. If you're doing nothing with a promise (awaiting, or catching), then you have bad code. You can read more about that here: https

• chrisseaton 6y ago
  That guide says that you should do this because it can cause race conditions: > This can cause unexpected and/or non-deterministic behavior depending on external timing factors. But, as this whole thread is about, sometimes you don't mind race conditions. So it can ok to acknowledge but ignore this advice if you are aware of how this race conditions matters to your codebase. Learn the rules, but know when to break them.