OptionFrame | 一款界面良好的弹出框

You only need to use async when you are using await in the same function. If there's await in a nested function, the parent function does not need async.

However, in your case, there is no function that should be made async in the first place.

• There is no benefit in awaiting any results in your function, because no code inside depends on any intermediary result. Just return the promises as you get them.
• There's no need for intermediary result variables like orderFrameArray, you're making things harder than they are with your approach of awaiting individual orders and pushing them to a top-level variable.
• Using await in a loop like you do inside your .map() call is bad for performance. You are basically serializing database access this way – the next query will only be sent after the current one has returned. This kind of daisy-chaining nullifies the database's ability to process multiple concurrent requests.
• getUserOrders2 is not Promise, it's Promise>.
• throw terminates the function anyway, you can do multiple checks for error conditions without using else if. This reduces nesting.

So a fully asynchronous function would look like this: