fix: unbreak bundling wretch #33
Merged
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
feri42
approved these changes
Apr 9, 2025
|
🎉 This PR is included in version 1.7.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
The current wretch logic is still broken with bundlers, even on 1.7.4.
See #32.
That's not the case,
wretch.browser.jsis CJS, not ESM.The real issue is that
require('wretch')is a function withx.default = x, so each time it's imported (either from'wretch',./wretch.browswer.js,./wretch.jsor anywhere else) some bundlers get confused and unwrap that to an object{ default : x }instead of a function.The only way to break that loop is to wrap the function, removing it's
.defaultproperty.This reverts the change from #32 and instead does that.