The library builds need optimization fix

[birdofpreyru]

The way these libraries are used afterwards, they only rely on Webpack compiled bundles.

[birdofpreyru]

My bad, only client-side uses the webpack bundle, and the server-side uses the compiled modules

[birdofpreyru]

But, do what extend the webpack bundles are used? Probably, the Webpack build just serves to compile SCSS...

[birdofpreyru]

The current understanding:

• At some point, only Webpack bundles were created and used both by the front- and back-end imports;
• Later it was changed with intention to rely on modules server-side, but the changed flawed, resulting in both library modules, and webbundle being bundled in the end-apps.
• It seems, it may be possible to not bundle JS in the libraries by webpack at all, but the problem is CSS - the current setup relies on library compilation by Webpack to correctly compile SCSS > CSS, and handling of CSS modules.

[birdofpreyru]

This needs to wait for the release of Webpack@5 and support of ES5 modules as library target in there. Then it will be possible to update the build process to bundle client-side code in a better way. Still need a separate server-side build.

[birdofpreyru]

After some more testing, this should not be a problem, if the entry point of a library is written in a very specific way, which allows Webpack to drop unnecessary code compile time in each particular case, and also allows Node to load the server-side version of the code.