Skip to main content

Angular Cache

Last week I got a call from our operations team indicating that one of our build server disks was filling up. While investigating what could be the root cause, I noticed the .angular folder for each of our Angular frontend applications.

I had no idea what this folder does, so let us find out together in this blog post…

TLDR; The .angular folder is used by the Angular CLI to cache the previous builds to reduce the build operations and improves the build time.

The .angular folder appeared in version 13 and is used as a disk cache by the Angular CLI to save a number of cachable operations on disk by default. When you re-run the same build, the build system restores the state of the previous build and re-uses previously performed operations, which decreases the time taken to build and test your applications and libraries.

If we look what is inside, we see 2 things:

  • An angular-webpack folder containing the binary files.
  • A babel-webpack folder containing all the text files in .json format.

According to the documentation the disk cache is only enabled for local environments. However you can change this value by  adding the cli.cache object to your Workspace Configuration. The object goes under cli.cache at the top level of the file, outside the projects sections.

{
"$schema": "./node_modules/@angular/cli/lib/config/schema.json",
"version": 1,
"cli": {
"cache": {
"environment": "local"
}
},
"projects": {}
}
view raw angular.json hosted with ❤ by GitHub

The value of environment can be one of the following:

  • all - allows disk cache on all machines.
  • local - allows disk cache only on development machines.
  • ci - allows disk cache only on continuous integration (CI) systems.

So far, so good. The strange this is that although it should only be enabled for local environments, the disk cache seems to be active on our build server as well.

The question is; how does Angular now the difference between our local and CI environment?

I found the answer while browsing through the Angular CLI source code. It checks if an environment variable named CI with a value of ‘true’ is present.

So I logged in on our build server and introduced this environment variable.

More information

Angular - ng cache

Labels

Labels:

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...
Read more