Use ESNext as default module system
#188
Merged
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
jonkoops
commented
Aug 5, 2023
jonkoops
commented
Aug 5, 2023
jonkoops
force-pushed
the
tsconfig-esnext
branch
from
0e1998f
to
8350b53
Compare
jonkoops
commented
Aug 6, 2023
jonkoops
commented
Aug 6, 2023
jonkoops
commented
Aug 6, 2023
frederikprijck
approved these changes
Aug 7, 2023
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.
Configures the TypeScript compiler to use
ESNextas the default module system, this allows the source imports to use the.jsextension, which is the standard method of importing modules. This PR also cleans up the TSConfigs by removing properties that are already configured, and by placing the configuration for the Rollup build in a separate file.