[package.json] Add "module" field #453
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
Codecov Report
@@ Coverage Diff @@
## master #453 +/- ##
======================================
Coverage 97.6% 97.6%
======================================
Files 3 3
Lines 292 292
======================================
Hits 285 285
Misses 7 7Continue to review full report at Codecov.
|
|
@cwelch5 @tmbtech please review when you can. This would close #403 (comment). |
tmbtech
approved these changes
Apr 25, 2019
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.
As mentioned in this comment on #403, the module field in package.json is a hint to bundlers (webpack, rollup, et al) to use the ES Module version of a package, when one is available.
Currently, by default, anybody using webpack is not getting the benefits of the ES Module build-- they're pulling in the CommonJS build.