proposal-top-level-await

The use case is not needing to wrap your code in an IIFE [1] when you would have a top-level await statement. It is useful in entry point of apps where you might need anything that uses async. It's also useful for having async modules. [2] They're also very helpful for debugging. Using await something in the console is way more convenient than something.then(). [1] https://developer.mozilla.org/en-US/docs/Glossary/IIFE [2] https://github.com/tc39/proposal-top-level-await/blob/HEAD/R...

Top level await is at stage 3: https://github.com/tc39/proposal-top-level-await Its in Typescript 3.8, Node 14.8 and probably in your Babel setup. I probably wont get to use Node 14 in prod for a while but I get by with a `main` function that has everything in that gets called at the bottom.

Yes, your example isn't complaining about then() being clearer than await (because it isn't) but rather complaining that top level await isn't everywhere yet. In other words, your complaints have disappeared in node, and will soon in browsers: https://github.com/tc39/proposal-top-level-await So yes: set(await get())

It's a stage 3 proposal[1], which according to the TC39 process[2] means "the solution is complete and no further work is possible without implementation experience, significant usage and external feedback." In other words, it's all but standardized. Barring significant blockers coming from actual implementation experience this will most likely be ratified. [1]: https://github.com/tc39/proposal-top-level-await [2]: https://tc39.es/process-document/

Did you read the commit? The spec material was linked: https://tc39.es/proposal-top-level-await/#sec-execute-async-... It's a Stage 3 proposal https://github.com/tc39/proposal-top-level-await