add browser field to package.json #97
Merged
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.
Resolves #95 and #96
This is a trivial change, but avoids the need for more in depth code change and could be made more verbose to better support es module loading in browser and node, with the addition of browser specific esm files:
The goal of this PR is just to get the loading working again for default packager configuration.
For example webpack loads for browser in the following order by default:
["browser", "module", "main"]and default for node is:["module", "main"].If anyone wants to use the module version, they should be able to do an override. This would help maintain backwards compatibility while leaving the module field still available.