Add top-level await for esnext and system modules #35813
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This removes our restriction around using an
await
expression at the top level of a file when the following conditions are met:--isolatedModules
is provided)--target
is >=ScriptTarget.ES2017
(minimum version required forawait
keyword)--module
is eitheresnext
orsystem
.This is not currently supported for earlier script targets (e.g., ES2016, ES2015, ES5, ES3) as the
system
transform currently happens after async functions and generators have been transformed, so it is too late to transform theasync function
that is created as part of thesystem
module transform. This also ensures it is consistent with--target es5 --module esnext
, as there would be no way to down-level theawait
in that context either.Fixes #25988, #32793