-
-
Notifications
You must be signed in to change notification settings - Fork 757
feat!: do not expose EsmLibraryPlugin to user directly, use modern-module instead #12792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for rspack-v2 canceled.
|
9ce9aa2 to
016ac5a
Compare
📦 Binary Size-limit
🎉 Size decreased by 318.50KB from 47.99MB to 47.68MB (⬇️0.65%) |
016ac5a to
d42c2f7
Compare
d42c2f7 to
5a7c39d
Compare
Rsdoctor Bundle Diff Analysis
Found 5 projects in monorepo, 5 projects with changes. 📊 Quick Summary
📋 Detailed Reports (Click to expand)📁 react-10kPath:
📦 Download Diff Report: react-10k Bundle Diff 📁 react-1kPath:
📦 Download Diff Report: react-1k Bundle Diff 📁 react-5kPath:
📦 Download Diff Report: react-5k Bundle Diff 📁 romePath:
📦 Download Diff Report: rome Bundle Diff 📁 ui-componentsPath:
📦 Download Diff Report: ui-components Bundle Diff Generated by Rsdoctor GitHub Action |
CodSpeed Performance ReportMerging this PR will degrade performance by 13.51%Comparing Summary
Performance Changes
Footnotes
|
5a7c39d to
62f0371
Compare
62f0371 to
bbf1b93
Compare
bbf1b93 to
72b6b01
Compare
Summary
Since v2.0, the EsmLibraryPlugin has already been used as the implementation of
modern-module, we shouldn't expose this plugin directly to the user but use config insteadRelated links
Checklist