You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I would like to use "top-level" await in a babel-node REPL. This is doable in vanilla Node with the --experimental-repl-await command line flag. Attempting to run babel-node with this flag currently results in:
error: unknown option `--experimental-repl-await'
Describe the solution you'd like
Support the Node --experimental-repl-await flag.
Describe alternatives you've considered
There's a top-level await TC39 proposal in the works, but it's still early (stage 2), with plenty of details to be worked out, and there is no Babel implementation yet (if ever?). The repl flag is already implemented in Node and much more limited in scope.
The text was updated successfully, but these errors were encountered:
Hey @noinkling! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.
If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.
Feature Request
Is your feature request related to a problem? Please describe.
I would like to use "top-level"
await
in a babel-node REPL. This is doable in vanilla Node with the--experimental-repl-await
command line flag. Attempting to runbabel-node
with this flag currently results in:Describe the solution you'd like
Support the Node
--experimental-repl-await
flag.Describe alternatives you've considered
There's a top-level await TC39 proposal in the works, but it's still early (stage 2), with plenty of details to be worked out, and there is no Babel implementation yet (if ever?). The repl flag is already implemented in Node and much more limited in scope.
The text was updated successfully, but these errors were encountered: