3 ms·

Oh my. Oh my. Please tell me there's some dead code elimination step in your pipeline too.

• laurent92 6y ago
  The dead code elimination step just drops the framework?
• Tade0 6y ago
  Here's the kicker: none of this is dead code. Vendor libraries alone take 28MB. Apparently one of the second order effects of rolling your own components is having enormous bundles because there's no incentive to minimize them. 3rd party libraries on the other hand usually go out of their way to be as small as possible. I'm doing my best not to be sarcastic about this. EDIT: we treeshake the bejesus out of it, but it's possible that there's some code duplication going on, because the build pipeline is, ahem, custom made.
  • ratww 6y ago
    What tech do you use? Also which kind of app is it? Does it have some special feature that causes the code bloat, or is it just lots of screens?
    • Tade0 6y ago
      Just Angular 10 and associated libraries. The app itself is a run-of-the-mill "tables, details and forms" SPA, but there are indeed a lot of screens. I see no reason why something like this should take so much space, but here we are.
      • ratww 6y ago
        Ah, gotcha! Thanks for answering. I've seen similar situations before. In my case it was mostly due to having a team that is larger than than necessary. Having multiple UI designers with differing opinions, developers that don't question redundancy in UI (or don't have time to check), managers that don't coordinate, and just communication problems in general. This led to a lot of reimplementation and duplicate code. In the end they changed the frontend framework a couple times, but the issue started creeping up again.