One thing to add - if anyone wants to prohibit all return await, and prefers const x = await foo; return x; (as suggested in #994 (comment)), I would recommend:

• use no restricted syntax selector: ReturnStatement > AwaitExpression;
• AND enable return-await with 'always'.

That way, neither return promise or return await promise will ever be legal, and you'll be forced to add an intermediate variable.

That is a better solution IMO than the 'never' option would have been, since the 'never' option still allows return promise.

I think if never is removed, it would be good to document what is said above and how to achieve same result.

That table that is worked on linked issue helps to understand these settings. But just a feedback, I think it’s not been very clear what the options do and when you want to use which option. I kinda thought that “never” would mean that you always need to return promise, I.e. you can’t return variable that was awaited earlier.

As a side note, I sometimes wish there was page where you could see list of useful syntax to disallow with some examples. There are a lot of cases where ban syntax would be enough instead of creating new rule. It’s just an option that it’s easy to forget.

As a side note, I sometimes wish there was page where you could see list of useful syntax to disallow with some examples.

#5863

But just a feedback, I think it’s not been very clear what the options do and when you want to use which option.

Fully agree! This and some of the other promise rules are an area of active focus for improving the docs, and clarity in general. 🙂