To me personally it is much more readable with the gutter indicators instead of additional await keywords inside the actual code but it has a drawback: you need an IDE that supports it. When reviewing code on gitlab/github there won't be any indicator.
https://typescript-eslint.io/rules/no-misused-promises/
https://typescript-eslint.io/rules/no-floating-promises/
They can catch some common mistakes. Of course these checks can only work reliably when you're using a typed language.
I'm still looking for one that forces me to put an await in front of every function call that returns a promise, unless I opt out.
The amount of effort JS programmers have to go to in order to write synchronous code that is legible, works and easy to understand is enormous. I am a Bad Programmer so accept that some of it is just my lack of willingness to spend the time to get over that hump but I find it almost impossible to believe the gains are worth the costs.
I also believe that you should see where asynchronous behavior can happen in your code. So from that angle i also appreciate the keyword and the coloring. Hidden resource access is pure evil.