create-svelte: update tsconfig to allow es2020 module and lib #817
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
module es2020?Currently, using dynamic imports with TypeScript results in:
Dynamic imports have been available unflagged since Node v12.17.
Why
lib es2020?Node v12.10+ has support for
String.prototype.matchAll,BigInt,Promise.allSettled, andglobalThis.Since we target Node v12.17+ for ESM support, this allows TS users to use the new builtins and dynamic imports without forcing
target es2020which lets the nullish coalescing operator??and optional chaining operator?.pass through and are undesirable.jsconfigdoes not need these changes.