Replies: 1 comment
-
|
Probably answer: It's expected; you need to keep the shared modules in the same cacheGroup that Module Federation uses ( |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
We're using Module Federation Enhanced's Shared Tree Shaking together with Rspack.
However, Shared Tree Shaking appears to stop working when custom
splitChunks.cacheGroupsare configured for chunk grouping.This creates a tradeoff:
With Shared Tree Shaking enabled and default chunking, builds generate a very large number of small chunks.
With custom s
plitChunks.cacheGroups, chunk count becomes manageable, but Shared Tree Shaking no longer seems to be applied.Is this limitation expected?
If so, is there a recommended way to make Shared Tree Shaking work together with custom
splitChunks.cacheGroups?If this combination is not currently supported, would you consider adding support for it in the future?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions