proposal-change-array-by-copy VS proposal-array-from-async

The new change array by copy methods (ES2023) will also work with tuples. So while you can't

Change Array by Copy

Stage 3 Change array by copy proposal offers methods like sortTo() that return a new array instead of mutating the original.

Note: there's a stage 3 proposal that introduces copy = arr.toSorted().

Change Array by Copy: Provides additional methods on Array.prototype and TypedArray.prototype to enable changes on the array by returning a new copy of it with the change.

The proposal is described here, with the other methods being:

Proposal, Polyfill

You're unlikely to see any new methods being added to JavaScript's Array that would modify an array in place like reverse() and sort() do. In fact some of the new methods that are being added are versions of reverse() and sort() (and splice()) that create copies rather than modifying the originals. Read more about them here: Proposal: Change Array by copy.

Since cloning is so common, a new specification has been written which has reached stage 3, which will give us a host of new ways to copy and then change an array. This proposal is called the "Change Array by Copy" proposal. Let's take a look at how it works.

Others have mentioned for await, which probably isn't ideal in the case of getting users by id since it'll only do one request at a time, which is less efficient. There's a proposal for Array.fromAsync() that'll essentially do the same thing...

Array.fromAsync: Array.fromAsync is to for await as Array.from is to for.

The proposal is described here.

It's only a stage 2 spec, but Array.fromAsync() would handle exactly what you want. Polyfill exists too.

Array.fromAsync: Like Array.from but it converts an async iterable (or a sync iterable of promises) to a promise that will resolve to an array.

Array.fromAsync Like Array.from but for async iterators.