Re-order export conditions #3
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
|
Wow, I had no idea Webpack was that strict with the ordering in that field. Thanks a lot for the PR, and please let me know about papercuts and issues with using this library, I'm sure there's plenty 😃 |
|
Released as v0.3.1 on npm/jsr 👍 |
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 going to sound so silly, but this issue is preventing me from using this project. Basically, Webpack gets really angry about the order of keys in the
exportsofpackage.json, it insists thedefaultMUST come last.Here are some other libraries that have run into this:
I'd love to use the library, but this is stopping me...