Release 3.2.1#428
Merged
Merged
Conversation
- fix(build): restore ESM output broken since v3.1.0 (#427)
|
david-ruiz-cko
approved these changes
Apr 22, 2026
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.
What
Patch release to fix the broken ESM output introduced in v3.1.0, which made the published package unusable under both
importandrequire.Changes
package.json— version bump to 3.2.1; removed--no-babelrcfrom build script to restore ESM output; addedpostbuildsmoke test; updated axios to^1.14.0package-lock.json— regenerated to reflect axios and version changesRoot cause
See #427 and #424.
--no-babelrcbypassed the Babel preset config (modules: false), causing the production build to emit CJS whilepackage.jsonstill declared"type": "module".Testing
dist/index.jsoutputs valid ESM after buildnpm cipassesRelated
Closes #424