[TOOLING]: Better webpack configurations

[evenstensberg]

Summary

Thread for discussing webpack configurations

[evenstensberg]

@unlikelyzero @ozyx I'm interested in your opinion of your production build. Do you need specific file endings/naming, or am I free to add minification and changes to the generated dist folder?

[evenstensberg]

Also forgot to mention, but the welcoming vibes from you on this project is very chill! Thank you! 🇺🇸

[unlikelyzero]

@evenstensberg interested to learn what all you can recommend.

minification would be great.

What sort of dist folder changes are you proposing?

[evenstensberg]

@unlikelyzero In the first iteration, I'd like to generate a good dist structure that groups images, js, html etc into respective folders. In addition to that, enable minification as far as possible without breaking your development flow. The reason why I was curious about it, was that I ought to think that you use a simple prod configuration so that bug tracking is easier. In production you cant easily debug since the generated source map is of another type. Did that make sense?

[evenstensberg]

Relative #6120

[evenstensberg]

@unlikelyzero How do you serve the OpenMCT application to consume? Do you have apache/nginx or do you just run webpack dev server?

[unlikelyzero]

https://github.com/scottbell/openmct-quickstart is our first attempt at publishing some of the best practices when using Apache @evenstensberg

[evenstensberg]

@unlikelyzero okay. Reason for asking is, that if you either spin up a express server with openmct, you can achieve some good performance benchmarks. Atm openmct is bundled to one file that is imported by your consumers, and naturally the size of the application will take longer to load.

[unlikelyzero]

The goal is to run this collection of performance tests https://github.com/unlikelyzero/openmct-performance

Against the OpenMCT-quickstart repo within 2 weeks.