It was closed as a duplicate, and that makes sense as there's another highly upvoted question that covers it: Wait until all promises complete even if some rejected
The problem is that 4 years and 9 months later, the top answer, selected answer, and even an answer that cover the modern functionality (from when it was a TC39 proposal) are out of date. There's a standard feature available in ECMAScript 2020 that provides the requested functionality.
I'd like nothing more than to edit the answers with the ECMAScript 2020 way, point to polyfills for backwards compatibility, and move on. That's where I ran into a little issue because it seems quite a few others would like nothing more than to do the same, and the edit queue is full. My next thought is "Well, time to help out!", but I can't work the edit queue. Editing is incorrect, I accept my concept of "small change" was at odds with the community and a new answer would be the appropriate way, but my later question still stands.
Frankly I see this as a pretty major detriment to the usefulness of SO in context of an ecosystem that sees improvements and growth so quickly. There is no way that the comment closest to the modern best answer will amass an additional ~300 upvotes to make its way to the top with anything but a user powered campaign along the lines of "Down with the superceded answers!" where we gather a critical mass of users to start looking for these questions and break the rules by brigading them to bring the newer best practices up to the top.
In the specific context of this duplicate I'm extremely happy to see another user was able to get an answer in regardless of the flagging and closure.
My question in a nutshell: What can we do when we can't do what's best for improving SO questions and answers by following the rules because the rules and system are too overloaded and won't allow us to help?