Luke Haas

There's currently no official Babel plugin for top-level await. When they release one I will certainly look into adding it.

Unfortunately that would result in the line-by-line output for top level code no longer being possible.

I'm not sure what you mean by that, but I'm certain there's no simple solution here.

https://www.chromestatus.com/feature/5767881411264512#:~:text=Allow%20the%20%60await%60%20keyword%20at,modules%20and%20exposes%20implementation%20details. Added above link to track when TLA is landing in Chromium

@hoegertn it's shipped with Chromium 89. RunJS is currently on Chromium 85. It's something I'll look further into after the upgrade. It's support is only in modules which may complicate...

@wc-matteo it's currently not possible due to upstream limitations. I'm very keen to support top-level await so if anything changes this will be top priority.

👍 will be good to have this at some point.

The 5 you're seeing is the ID that gets returned from `setTimeout`.

@btecu the ID that gets returned by `setTimeout` won't always be the same.

Please provide your debug log. You can access this from the Help menu:  Also, is your CPU Intel or Apple?