We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description
Currently when using REPL for debugging some library's async methods is painful
> asyncTaskThatResolvesNumber(); Promise<pending> // nodejs repl > await asyncTaskThatResolvesNumber(); await asyncTaskThatResolvesNumber() ^^^^^
Current workaround is
> asyncTaskThatResolvesNumber().then(console.log) 123
Desired Behaviour
Chrome's console handles the case as follows.
> asyncTaskThatResolvesNumber(); Promise<pending> // chrome console > await asyncTaskThatResolvesNumber(); 123
It'd be very helpful if we can do that in NodeJs REPL.
The text was updated successfully, but these errors were encountered:
TLA in REPL has been supported experimentally behind flag --experimental-repl-await. You can enable it with node --experimental-repl-await.
--experimental-repl-await
node --experimental-repl-await
Refs: https://nodejs.org/dist/latest-v16.x/docs/api/cli.html#cli_experimental_repl_await
Sorry, something went wrong.
Wow that's awesome! Thank you. So I shall close this.
Though is it known approximately until when this will stay experimental? Because it seems that it works great.
@zemse
There is no ETA to unflag this right now. In the discussion on #34733, it seems still too early to unflag.
No branches or pull requests
Description
Currently when using REPL for debugging some library's async methods is painful
Current workaround is
Desired Behaviour
Chrome's console handles the case as follows.
It'd be very helpful if we can do that in NodeJs REPL.
The text was updated successfully, but these errors were encountered: