Add a browser-only export for Web clients #9
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 package has a single export that includes both NodeJS and browser modules. When a web project imports this library, the bundler also imports the NodeJS-only modules, which generates a bunch of warnings, like this in vite:
We can clean this up by creating a special browser-only export. Bundlers like Vite and Webpack know to choose the 'browser' export in projects that are web-only (not NodeJS).
This change adds a 'browser' export and updates the documentation to use browser-only examples.
Clients don't need to change anything to benefit from this new export. The bundlers should just see the 'browser' export and use it automatically, but the warning spew will disappear.