fix: improve CommonJs bundle to ESM library#19847
Merged
alexander-akait merged 2 commits intomainfrom Sep 1, 2025
Merged
Conversation
CodSpeed Performance ReportMerging #19847 will degrade performances by 64.41%Comparing Summary
Benchmarks breakdown
|
| parser.state.module.addDependency(dep); | ||
| /** @type {BuildMeta} */ ( | ||
| parser.state.module.buildMeta | ||
| ).treatAsCommonjs = true; |
Member
There was a problem hiding this comment.
Let's rename treatAsCommonjs to treatAsCommonJs 😄
alexander-akait
approved these changes
Aug 29, 2025
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 kind of change does this PR introduce?
Part of fix 💎Nice CommonJS modules are converted to ESM and also includes some refactoring to
ExportPropertyLibraryPlugin/ModuleLibraryPlugin.When the entry module is commonjs, we now generate default export pointing to webpack_exports, along with all named exports, aligning with the behavior of cjs-module-lexer.
Did you add tests for your changes?
Yes
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?
No