Remove incorrectly used browser field #1573
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
|
This pull request is being automatically deployed with ZEIT Now (learn more). 🔍 Inspect: https://zeit.co/markedjs/markedjs/hetghzz43 |
UziTech
approved these changes
Dec 4, 2019
This was referenced Dec 20, 2019
This was referenced Apr 22, 2020
zhenalexfan
pushed a commit
to zhenalexfan/MarkdownHan
that referenced
this pull request
Nov 8, 2021
Remove incorrectly used browser field
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.
This is a common misconception - but browser field is not for pointing to a fully browser-compatible file (like in your case you have wanted to point with it to the UMD bundle). It exists to alias files depending on node-specific modules/APIs to files that can be used in browsers (so for example with node-specific modules/APIs stubbed) after bundling etc.
For example webpack picks "browser" field over "module" by default if provided and that kinda makes "module" file not-used - but the intention is to actually use it.
As you don't depend on any node-specific stuff the appropriate course of action is to just remove this field from your package.json