My misunderstanding of Promise.all
For a long time I thought Promise.all was used to fire and run promises concurrently.
Every time I encountered code that used two awaits, I always proposed using Promise.all instead. Now, this still holds true, but ...

Tiger's Place

The post clarifies the common misconception about `Promise.all` in JavaScript, which waits for multiple promises to resolve and returns their results in an array. It explains how `await` works as syntactic sugar and how `Promise.allSettled` provides a way to handle all promises' results, including rejections, for better debugging. Practical examples demonstrate how to use these methods effectively.

I misunderstood Promise.all in JavaScript

Permalink My misunderstanding of Promise.all

Permalink Promise.allSettled with Promise.all

In the “using the same promise” example, you’re awaiting the initial promises, so you’re just passing the values to Promise.all, not the actual promises, or in other words, you don’t need Promise.all at all, you can just reuse the values.
In the allSettled example, once settled, the promise will be resolved. Therefore you don’t need the final Promise.all and can just return “results”.

Please let me know if I get it right. If I call an async function again and again, it will create new promises. But if I call them once and store their output in a variable (I think reference them to a variable will be a better word since we are not storing the promise’s resolved value, for that we use ‘then’ method), I can use this variable to access the promise without running it again and again.
Now if I want to run promises concurrently, I would usually use promise.all, but that gets hard to debug. So what I should do instead is that I call the async function once, pass on it’s reference to the settled method, for debugging and then pass on the same reference to promise.all, and then handle the output as I usually do. This way I have easier debugging without repeatedly running and promises. Did I get it right?

I might be completely misunderstanding something here, but you are using await and assigning the value to a variable. You then call promise.all using that value, but it is not a promise. It is the result of the async call.
Am I just totally missing something here? I will have to test it out but this does not make sense as implemented calling promise.all on a random value won’t be doing any actual work is like saying promise.all([1,2]) they are settled values nothing async about it.
But like I said, I am probably totally misunderstanding something.