Use new format instead of legacy #1
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
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.
"es" and "esm" are both formats for ECMAScript modules.
"es" is a legacy format that was used before the introduction of the "esm" format. It is a simple format that does not support all the features of modern ES modules. For example, it does not support dynamic imports.
"esm" is a newer and more advanced format that is designed to work with modern ES modules. It supports all the features of ES modules, including dynamic imports, export renaming, and export namespace objects. It is the recommended format for building modern JavaScript libraries and applications.