Fix npm package resolution by adding exports field to package.json#6158
Open
alexgleason wants to merge 1 commit intoplausible:masterfrom
Open
Fix npm package resolution by adding exports field to package.json#6158alexgleason wants to merge 1 commit intoplausible:masterfrom
alexgleason wants to merge 1 commit intoplausible:masterfrom
Conversation
This file contains hidden or 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
1 participant
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.
Changes
Add
exportsfield to the npm package'spackage.json. The package currently only declaresmodule(nomainorexports), which causes modern bundlers like Vite and SvelteKit to fail with:The
modulefield is kept for backward compatibility with older bundlers.Fixes #5879
See also: https://publint.dev/@plausible-analytics/tracker@0.4.4
Tests
Changelog
Documentation
Dark mode