fix: Bump tsconfig target to es2017 to avoid polyfilling await #567
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.
Currently the
target
in thetsconfig.json
file it set to ES2015, which means that the TypeScript compiler is polyfilling theawait
keyword inlib/utils/parser-config-resolver/worker.ts
because it is an ES2017 language feature.To avoid that happening this pull request bumps the target in the
tsconfig.json
file to ES2017. This is a non-breaking change as this package dropped Node.js versions older than 18 in version 3.0.0 and Node.js 18 supports ES2022 language features.Before and after diff of
dist/utils/parser-config-resolver/worker.js
: