provide a default entry point for ES modules, fixes #37#38
Conversation
This makes it possible to import the package from a pure ESM context.
Member
|
I'm not sure how this would fix the issue since the file build/index.js isn't referenced anywhere. I put up #41 which uses export =. It's on npm as 1.7.0-rc.0. Could you try it and let me know if it works in your project? |
Author
|
I checked 08eb4b7 and it works fine, thanks! Will close this PR then, not sure what caused it to work. |
Member
|
Thanks for checking. Published to npm as 1.7.0. |
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
2 participants
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 makes it possible to import the package from a pure ESM context.
Please do test in your local environment!