TL;DR: I want to reduce resulting JavaScript code size by mangling privates — what technology stack to use?Infrastructure for building a front-end project consists of a lot of parts, but I'd like to focus on bundling & code size. I'm obsessed with code size optimizations, but I still want to have a nicely organized modular code.Mainstream tools like WebPack do a great job eliminating dead...
INTROThere are bunch of tools for static code analysis in JavaScript. For the sake of simplicity, I'll split them in two large groups: eslint et al, which works at the level of one file and type analysers: ternjs, flowtype and even typescript. Tools in the former group need to know how to resolve modules and usually rely on the folder structure. Unfortunately, in enterprise development it's...
I feel some need for code examples as well [as other commenters], but I'm afraid the post would be bloated with them. Maybe, it's worth expanding that into a series of posts - one per architecture/approach.
Another idea to improve expressiveness of the post would be to draw e.g. ol'good MVC pattern for comparison. But since your article is targeted for people familiar with the subject, that piece of advice might be not very useful.
As for conclusion, I think I cannot completely agree. It seems for me a little like a "silver bullet" solution. On top of that, looking at charts, I can think about a potential problem. Proposed solution requires a lot of internal wiring, which can result in a bunch of glue code.
I think that different solutions suit different application patterns. E.g. ones go well with -bacon and cheese- unconnected models/stores, the others benefit from centralized data hub.
You've started a really interesting topic, but we need to go further. We can benefit more from a deeper analysis.