Slow builds stop developers' productivity cold. If code takes even two minutes to compile, it’s easy to get distracted. You lose your train of thought or, god forbid, open social media.
Slow builds are also expensive. Imagine you have one developer paid $100,000 a year, approximately the average salary of a software engineer in the United States. That’s $50 an hour, assuming they get two weeks off and work 40 hours a week. If they rebuild the app ten times a day and each rebuild takes two minutes, that person is paid $3,320 per year to watch a progress bar. And that’s not even factoring in the cost of running builds on cloud infrastructure.
No wonder a Reddit engineer announced last year that they were buying new Apple Silicon MacBook Pros for their Android developers. According to this engineer, the improved build times paid for the laptops in just three months.
So if you are running into slow Angular builds, try these steps to reduce build time. They are listed in order of increasing complexity.
Step 1: Update your local environment
First, increase Node’s memory limit. This consumes more RAM, but it helps.
Second, keep ahead-of-time (AOT) compilation turned on. Builds will take slightly longer than just-in-time (JIT) compilation, but the page will refresh so quickly that it may be worth it.
Step 2: Check your build process
I tested every command-line option for ng build for its performance while enabled and disabled. These are the flags I’d recommend using, depending on the context.
|
Dev only |
Prod only |
|---|---|
|
--named-chunks |
--build-optimizer |
|
--vendor-chunk |
--optimization |
|
|
--output-hashing |
|
|
--extract-licenses |
|
|
--subresource-integrity |
--named-chunks and --vendor-chunk help cache JavaScript bundles across builds. The flags in the prod column tend to optimize the build for smaller bundle sizes at the expense of compile time.
Try hot module reloading.
Hot module reloading (HMR) is much easier in Angular 11. When Angular rebuilds a module, it updates the app without reloading the page. It just swaps in new code.
However, use caution as it has strange behaviour with RxJS subscriptions and WebSockets. If you don’t correctly unsubscribe from either, it could create duplicate connections and confusing errors.
Step 3: Minimize the work required
Builds are faster if there’s less code. Consolidate components, delete old code and get rid of what you can.
Avoid custom build processes
Our team of Angular experts worked with one client whose builds were being slowed by localization files. They had eschewed Angular’s localization system for a custom process that combined over a thousand JSON files at build time.
Avoid adding extra steps to the build process where possible. If Angular includes some functionality, use it instead of rolling your own. Using built-in features, whether localization or scripting or bundling, will give you the benefit of work done by the Angular team to optimize build times.
If you have some pressing product needs and need to do a custom process during the build, consider whether that step can be done asynchronously.
Use small modules
Lastly, use small Angular modules. When an Angular application is being served, and a file changes, only the module containing that file is rebuilt.
Step 4: Upgrade Angular
Angular, unlike other frameworks, includes batteries. With React or Svelte, you can use a completely different and faster compiler. Create-React-App might start you with webpack, but you can speed up esbuild.
With Angular, the compiler the framework ships is the one you get. Updating to new major versions of Angular will get you faster, with fewer buggy compilers with better build times. Angular 9 and Ivy are especially fast.
When you do the upgrade, be sure to use ng update. The Angular CLI will apply migrations to your build config to automatically use the fastest settings. After the upgrade, you can also run these migrations (ng update @angular/cli --migrate-only).
Now, upgrading major Angular versions is easier said than done. Sometimes you’re working on a massive old enterprise app, and there’s just no time or budget to upgrade.
If you need help upgrading your Angular app fill out our form to get a free consultation! See also our guide to migrating tslint to eslint.
Step 5: Use caching
Tools like Nx also cache build data in the cloud and share it among developers. They can be compelling if you don’t mind introducing another dependency to the build process.
If your builds are bottlenecked specifically during continuous integration, try caching your node_modules folder. People have reported up to 75% faster builds from preserving node_modules between CI runs.
Step 6: Get help from the professionals.
Still can’t get build times where you want them? Get help from Bitovi’s team of Angular experts. They’ve worked with small, medium and large Angular applications and can meet your team’s needs. Or ask a question in Bitovi's Discord Community.
javascript
