3 ms·

I wish the Angular team put some work into integrating. They are instead doubling down on webpack which is frustrating. After they back stepped regarding the ba

by jamra 6y ago

I wish the Angular team put some work into integrating. They are instead doubling down on webpack which is frustrating. After they back stepped regarding the bazel build system I thought that all was lost. Then this beauty came out. Unfortunately it's not as interesting as the incremental compiler.

deanclatworthy 6y ago
It's still early days for esbuild. If you follow the commit history there are still some weird bugs. I'd give it a few months to get these things ironed out (along with wider usage) and it'll be good to go.
- jamra 6y ago
  That would make my day. I have a 64GB RAM PC because I work on 2 or 3 angular apps at a time and since my PC is the fastest I also use it for CI builds on occasion. It's a nightmare to wait 20 minutes for an optimized prod build. And having to upgrade everyone's RAM so they can contribute to the front end is horrible. We are past 10GB of RAM required to start the dev server.
  - nicoburns 6y ago
    10GB!! How big is this project!? Could you split it up somehow?
    - jamra 6y ago
      We actually just worked on splitting it up into libraries. The shared library might actually make the ending build larger due to it being potentially duplicated (I'm not certain about this until I test it). Unfortunately that has to go on hold temporarily. It is a large Healthcare application in the therapy space. The ending build is actually fine, but the tooling eats RAM like something else. Little by little I take large third party libraries and rewrite them on my own to drop 5MB includes. I'm sure that is part of it. Devextreme and Syncfusion are libraries I would strongly recommend avoiding.
      - jeremycarter 6y ago
        Syncfusion added 15MB to my bundle size :( I like their components but they aren't lightweight by any means.
kylecordes 6y ago
Incidentally, a new version of the Bazel rules_nodejs, which somewhat confusingly has both browser and no JavaScript support, includes an esbuild rule. As for Angular CLI which relies heavily on web pack, it has years of grinding tweaking bug fixing work getting all the right behaviors for all the cases. It's going to take a lot to re-create that in a non-breaking way using something different under the hood.

by jamra 6y ago

deanclatworthy 6y ago

It's still early days for esbuild. If you follow the commit history there are still some weird bugs. I'd give it a few months to get these things ironed out (along with wider usage) and it'll be good to go.

jamra 6y ago
That would make my day. I have a 64GB RAM PC because I work on 2 or 3 angular apps at a time and since my PC is the fastest I also use it for CI builds on occasion. It's a nightmare to wait 20 minutes for an optimized prod build. And having to upgrade everyone's RAM so they can contribute to the front end is horrible. We are past 10GB of RAM required to start the dev server.
- nicoburns 6y ago
  10GB!! How big is this project!? Could you split it up somehow?
  - jamra 6y ago
    We actually just worked on splitting it up into libraries. The shared library might actually make the ending build larger due to it being potentially duplicated (I'm not certain about this until I test it). Unfortunately that has to go on hold temporarily. It is a large Healthcare application in the therapy space. The ending build is actually fine, but the tooling eats RAM like something else. Little by little I take large third party libraries and rewrite them on my own to drop 5MB includes. I'm sure that is part of it. Devextreme and Syncfusion are libraries I would strongly recommend avoiding.
    - jeremycarter 6y ago
      Syncfusion added 15MB to my bundle size :( I like their components but they aren't lightweight by any means.

kylecordes 6y ago

Incidentally, a new version of the Bazel rules_nodejs, which somewhat confusingly has both browser and no JavaScript support, includes an esbuild rule. As for Angular CLI which relies heavily on web pack, it has years of grinding tweaking bug fixing work getting all the right behaviors for all the cases. It's going to take a lot to re-create that in a non-breaking way using something different under the hood.