Support for multi-config compilation

[IIIristraM]

💬 Questions and Help

I'm using a monorepo approach, where client consists of multiple packages with their own webpack configurations, but all bundles dynamically extends single application, which is hosted on nodejs server.

So each package produce its own loadable-stats.json, and for dev build I'm using webpack-dev-middleware with multicompiler.

I found no clues in documentation on whether any conventional way to extract chunks in such configuration, so I would appreciate any advice on how to make loadable-components work for multiple stats files.

[open-collective-bot]

Hey @IIIristraM 👋,
Thank you for opening an issue. We'll get back to you as soon as we can.
Please, consider supporting us on Open Collective. We give a special attention to issues opened by backers.
If you use Loadable at work, you can also ask your company to sponsor us ❤️.

[theKashey]

I can not provide and solution as well. There is an attempt to use loadable-components with module federation - #575, but it's actually NOT working

May be @7rulnik knows more about it.

[kdevan]

This example project helped me: https://github.com/gregberge/loadable-components/blob/master/examples/server-side-rendering/src/server/main.js

[IIIristraM]

As far as I understand, now the only possible solution is to create ChunkExtractor for each stats file, which means that for N files application has to be rendered N times to collect chunks from all builds.

[theKashey]

You can create multiple chunk extractors on the server side but it might not work that way on the client side, where any code is executed inside some particular webpack "instance".

If you want to "mix" different builds/apps together - you need module federation.

[7rulnik]

@theKashey it works with node target, but currently it's impossible to predict some assets on the client-side. Not a big issue but still annoying.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.