Skip to content
This repository has been archived by the owner on Oct 2, 2021. It is now read-only.

Support top-level await in console #353

Open
roblourens opened this issue Sep 11, 2018 · 6 comments
Open

Support top-level await in console #353

roblourens opened this issue Sep 11, 2018 · 6 comments
Assignees

Comments

@roblourens
Copy link
Member

microsoft/vscode#38316

Need to detect when the console input starts with await, wrap in an async IIFE, and set awaitPromise on Runtime.evaluate to true.

@roblourens
Copy link
Member Author

I'm not sure what happens in older runtimes that don't support async/await or awaitPromise.

@fescobar
Copy link

Hi @roblourens do you have any ETA for this?
Thank you so much

@CodeWarriorr
Copy link

+1

1 similar comment
@yabloki
Copy link

yabloki commented Jun 22, 2019

+1

@cefn
Copy link

cefn commented Oct 4, 2019

Is there a way to configure a vscode debug launch session to simply enable the --experimental-repl-await flag behind the scenes?

I tried adding it to the runtime args of the node VM running the debugged code, but it didn't change the behaviour, although I can prove the flag works on that VM interactively (allows top-level await).

However, I may not understand exactly how the debug console session comes into existence. If it's not a repl in a node VM then that may be why I can't enable it. Are there other flags which control the debug-session VM?

@roblourens
Copy link
Member Author

Params in args in the launch config will be passed to node.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants