fix: resolve ModuleNotFoundError in ESM environments by generating native bundles#1299
Merged
remarkablemark merged 9 commits intoremarkablemark:masterfrom Jan 26, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1299 +/- ##
=======================================
Coverage 93.10% 93.10%
=======================================
Files 7 7
Lines 145 145
Branches 30 30
=======================================
Hits 135 135
Misses 8 8
Partials 2 2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This was referenced Jan 26, 2026
Owner
|
Looks like this caused a regression #1317 |
4 tasks
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
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 is the motivation for this pull request?
This PR fixes the ModuleNotFoundError encountered in strict ESM environments and web-based bundlers (like CodeSandbox/Sandpack).
The issue was caused by the esm/ directory containing manually created .mjs wrapper files that performed cross-directory imports from the CommonJS lib/ directory using relative paths (e.g., import ... from '../../lib/...'). Many modern bundlers fail to resolve these cross-format internal references.
Fixes #1222
What is the current behavior?
CodeSandbox
Checklist: