Open easy1090 opened 5 months ago
Since this is on the rust end, it would be best to reference this in a issue to rspack core directly
Since this is on the rust end, it would be best to reference this in a issue to rspack core directly
yes, The above project is of rspack, I'll also post a issue on rspack repo. But I found that mf core has the same container module identifier generation logic:https://github.com/module-federation/core/blob/main/packages/enhanced/src/lib/container/ContainerEntryModule.ts#L98
It would be great if it could be optimized.
Stale issue message
im reluctant to alter the identifier as other things in the ecosystem or other plugins outside my ecosystem rely on the stats identifiers to unpack the configurations specified for federation. Do you have a snippet of the json that shows the long ids?
Describe the bug
When rsdoctor analyzed a certain business MF project, the build analysis was very slow. It was found that the stats.json containing chunks and modules was nearly 4G, and that each module's issuer path contained the container entry module, and the identifier of the container entry module was 22KB, that string contains 100+ arrays and there were a total of 13,000 modules, resulting in a very large stats.json, which caused rsdoctor to analyze very slowly using stats.json.
But, this issue found from a certain business MF project on rspack, but MF core and rspack mf has same logic on generating the identifier of the container entry module.. So I think if iIcan post a issue on MF directly. Thanks ~
We are looking forward to optimizing the issue of overly long identifiers of the container entry module of the issuerPath in the Stats.json file.
Used Package Manager
pnpm
System Info
Validations