-
Notifications
You must be signed in to change notification settings - Fork 2.6k
fix(module-federation): do not rely on virtualRuntimeEntry #31831 #32387
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
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
View your CI Pipeline Execution ↗ for commit 468ff1e
☁️ Nx Cloud last updated this comment at |
caddeae
to
933b4bd
Compare
933b4bd
to
d52d581
Compare
d52d581
to
b78ed68
Compare
b0a27b2
to
7ad3170
Compare
7ad3170
to
7cc02ac
Compare
7cc02ac
to
0d91630
Compare
0d91630
to
bbadfc3
Compare
1483235
to
9b654fb
Compare
9b654fb
to
f82a2f6
Compare
f82a2f6
to
0180f30
Compare
0180f30
to
468ff1e
Compare
…2387) Previously, we needed to rely on `virtualRuntimeEntry` to allow builds between caching to operate successfully. In more recent version of `@module-federation/enhanced` this is no longer the case. By setting this option, it is now inflating the size of the bundles produced by Webpack and Rspack As it is no longer a strict requirement, remove it. Users can still set it manually if they run into issues Fixes #31831 Fixes #32404 (cherry picked from commit b8f9a95)
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
Previously, we needed to rely on
virtualRuntimeEntry
to allow builds between caching to operate successfully.Expected Behavior
In more recent version of
@module-federation/enhanced
this is no longer the case.By setting this option, it is now inflating the size of the bundles produced by Webpack and Rspack
As it is no longer a strict requirement, remove it.
Users can still set it manually if they run into issues
Related Issue(s)
Fixes #31831
Fixes #32404