hel VS MAL-Cover-CSS

Toolchain-independent sdk-based module federation hel-micro

helux is a zhuang't that encourages service injection and supports responsive changes to react. Its predecessor is concent (a high-performance state management framework for Vue-like development experience), but concent itself needs to be compatible with class and function to maintain a consistent syntax, and for its setup function, internal The amount of code is too large. After compression, there are more than 70 more than KB, and the API is exposed too much, which leads to a sharp increase in learning difficulty. It was originally designed as a lightweight react data flow solution that encourages service injection, supports responsive changes, and supports dependency collection.

It is highly recommended to try hel micro(https://github.com/tnfe/hel) in turbo，cause hel-micro is a runtime module federation SDK which is unrelated to tool chain, so any tool system can access module federation technology in seconds .

The module federation can play an even more powerful role in the construction of super-large js projects, and the module deployment efficiency and sharing efficiency of giant applications will be easily solved. At the same time, it is matched with micro-container related frameworks (such as wujie, rame), etc., to ensure your isolation operation requirements. Escort, welcome to star hel-micro, understand and use it.

You can cut down the duplicate config with webpack-merge package. I start with a common config object that defines loaders, aliases, etc. and it gets imported by my frontend/backend/cronjob/worker targets that simply describe the entry/outputs

I also recommend using ts-node and write your configs in Typescript to avoid typos

Here's an old side project of mine that has 3 targets [1]. I personally don't think it's that complex but it does have hundreds of lines altogether.

[1] https://github.com/Trinovantes/MAL-Cover-CSS/tree/master/bui...