All Posts

I originally published this blog post with my colleague Patrick Surrey on the LeanIX Engineering Blog.

Each frontend in our nx monorepo has its own workflow for running CI checks and deployment. The default nx affected behaviour does not enable us to only get the list of projects that are affected and used by a specific application.

So we wrote a GitHub Action that does just this: leanix/nx-affected-dependencies-action.

Go to the action repository

Go to the action on the GitHub Marketplace

Our main motivation for this action was to speed up the releases of our frontend applications and to save time and money on continuous integration checks.

The solution: By combining the nx affected and nx dep-graph --focus=theNameOfTheAppToDeploy commands we can create an intersection of these two lists to only get the affected projects that are actually a dependency of theNameOfTheAppToDeploy.

Different lists of projects produced by three individual nx commands

How to use it

This is just one way to use the leanix/nx-affected-dependencies-action in your workflows. It resembles the use case of merging a feature branch into your main branch and comparing the changes of the latest commit on main (${{ github.sha }}~1) with the merge commit of your feature branch (${{ github.sha }}).
For a more detailed overview, including a gitflow parameter, please see the project README.

- name: Evaluate affected
uses: leanix/nx-affected-dependencies-action@v0.2.1
id: affected
project: pathfinder
base: $~1
head: $

- name: Run Unit Tests (Affected)
if: steps.affected.outputs.isAffected == 'true'
affectedDeps: $
run: npx nx run-many --target=test --projects=$affectedDeps --runner ci

The nx run-many command will run the given target task on the provided projects, which in this case come from the affectedDeps output of the leanix/nx-affected-dependencies-action.


As of the time of writing we are shipping 13 individual angular applications in our nx monorepo. Our CI tool of choice is GitHub Actions.
All our microfrontends will be deployed after a feature branch is merged and CI checks are green.

The most time consuming application in our monorepo is our "shell application". Among "normal shell application things" like the navigation bar it has the largest chunk of code of any application, since it was there long before we started adopting microfrontends.

How we used to do it

This is a simplified version of the Test step in the workflow of a microfrontend when a feature branch is merged:

- name: Test
run: npx nx affected:test --base=$~1 --head=$ --runner ci

As you can see we used the nx affected command to lint and test the projects affected by the merged changes before deploying the new version of a frontend. However this resulted in each frontend application workflow unnecessarily linting and testing projects that are not used by them, but other applications.

Take a change in our shared component library for example: almost all of our applications will be affected by this. Now our small todos microfrontend will redundantly lint and test the large "shell application" and code of other microfrontends, as these are also inside the list of projects returned by nx affected.

Our nx cache does save us a significant amount of time spent on GitHub Actions, but the nx affected situation definitely wasn't desirable.


Here is a comparison of the amount of projects to check and their duration for our microfrontends when our shared component library was changed.

Todos microfrontend:
nx affected: 62 projects in ~12 minutes
nx-affected-dependencies-action: 13 projects in ~3 minutes

Indicators microfrontend:
nx affected: 62 projects in ~12 minutes
nx-affected-dependencies-action: 6 projects in ~1 minute

This means the Todos release is now completed 9 minutes faster and Indicators 11 minutes faster than before.

Published 06 Dec 2021