nx/docs/shared/migration/migration-angular.md

Migrating an Angular CLI project to Nx

Within an Nx workspace, you gain many capabilities that help you build applications and libraries. If you are currently using an Angular CLI workspace, you can transform it into an Nx workspace.

Migrating to a Standalone Angular App with Nx

You can migrate to a Standalone Angular App with the command:

npx nx@latest init

This command will install the correct version of Nx based on your Angular version.

This will enable you to use the Nx CLI in your existing Angular CLI workspace while keeping your existing file structure in place. The following changes will be made in your repo to enable Nx:

• The nx, @nx/workspace and prettier packages will be installed.
• An nx.json file will be created in the root of your workspace.
• For an Angular 14+ repo, the angular.json file is split into separate project.json files for each project.

Note: The changes will be slightly different for Angular 13 and lower.

Migrating to an Integrated Nx Monorepo

If you want to migrate your Angular CLI project to an Integrated Nx Monorepo, run the following command:

npx nx@latest init --integrated

The command applies the following changes to your workspace:

• Installs the nx, @nx/angular and @nx/workspace packages.
• Moves your applications into the apps folder, and updates the relevant file paths in your configuration files.
• Moves your e2e suites into the apps/<app name>-e2e folder, and updates the relevant file paths in your configuration files.
• Moves your libraries into the libs folder, and updates the relevant file paths in your configuration files.
• Updates your package.json scripts to use nx instead of ng.
• Splits your angular.json into project.json files for each project with updated paths.

After the changes are applied, your workspace file structure should look similar to the one below:

<workspace name>/
├── apps/
│   └─ <app name>/
│       ├── src/
│       │   ├── app/
│       │   ├── assets/
│       │   ├── favicon.ico
│       │   ├── index.html
│       │   ├── main.ts
│       │   └── styles.css
│       ├── project.json
│       ├── tsconfig.app.json
│       └── tsconfig.spec.json
├── libs/
│   └── <lib name>/
│       ├── src/
│       ├── ng-package.json
│       ├── package.json
│       ├── project.json
│       ├── README.md
│       ├── tsconfig.lib.json
│       ├── tsconfig.lib.prod.json
│       └── tsconfig.spec.json
├── tools/
├── .editorconfig
├── .gitignore
├── .prettierignore
├── .prettierrc
├── karma.conf.js
├── nx.json
├── package.json
├── README.md
└── tsconfig.base.json

Modified Folder Structure

The automated migration supports Angular CLI workspaces with a standard structure, configurations and features. It supports workspaces using the following executors (builders):

• @angular-devkit/build-angular:application
• @angular-devkit/build-angular:browser
• @angular-devkit/build-angular:browser-esbuild
• @angular-devkit/build-angular:dev-server
• @angular-devkit/build-angular:extract-i18n
• @angular-devkit/build-angular:karma
• @angular-devkit/build-angular:ng-packagr
• @angular-devkit/build-angular:prerender
• @angular-devkit/build-angular:protractor
• @angular-devkit/build-angular:server
• @angular-devkit/build-angular:ssr-dev-server
• @angular-eslint/builder:lint
• @cypress/schematic:cypress
• @nguniversal/builders:prerender
• @nguniversal/builders:ssr-dev-server

Support for other executors may be added in the future.

After migration

Your workspace is now powered by Nx! You can verify that your application still runs as intended:

• To serve, run nx serve <app name>.
• To build, run nx build <app name>.
• To run unit tests, run nx test <app name>.
• To see your project graph, run nx graph.

Your project graph will grow as you add and use more applications and libraries. You can add the --watch flag to nx graph to see the changes in-browser as you add them.

Set Up CI for Your Angular Workspace

This tutorial walked you through how Nx can improve the local development experience, but the biggest difference Nx makes is in CI. As repositories get bigger, making sure that the CI is fast, reliable and maintainable can get very challenging. Nx provides a solution.

• Nx reduces wasted time in CI with the affected command.
• Nx Replay's remote caching will reuse task artifacts from different CI executions making sure you will never run the same computation twice.
• Nx Agents efficiently distribute tasks across machines ensuring constant CI time regardless of the repository size. The right number of machines is allocated for each PR to ensure good performance without wasting compute.
• Nx Atomizer automatically splits large e2e tests to distribute them across machines. Nx can also automatically identify and rerun flaky e2e tests.

Generate a CI Workflow

If you are starting a new project, you can use the following command to generate a CI workflow file.

npx nx generate ci-workflow --ci=github

{% callout type="note" title="Choose your CI provider" %} You can choose github, circleci, azure, bitbucket-pipelines, or gitlab for the ci flag. {% /callout %}

This generator creates a .github/workflows/ci.yml file that contains a CI pipeline that will run the lint, test, build and e2e tasks for projects that are affected by any given PR.

The key line in the CI pipeline is:

- run: npx nx affected -t lint test build e2e-ci

Connect to Nx Cloud

Nx Cloud is a companion app for your CI system that provides remote caching, task distribution, e2e tests deflaking, better DX and more.

To connect to Nx Cloud:

• Commit and push your changes
• Go to https://cloud.nx.app, create an account, and connect your repository

Connect to Nx Cloud Manually

If you are not able to connect via the automated process at https://cloud.nx.app, you can connect your workspace manually by running:

npx nx connect

You will then need to merge your changes and connect to your workspace on https://cloud.nx.app.

Enable a Distributed CI Pipeline

The current CI pipeline runs on a single machine and can only handle small workspaces. To transform your CI into a CI that runs on multiple machines and can handle workspaces of any size, uncomment the npx nx-cloud start-ci-run line in the .github/workflows/ci.yml file.

- run: npx nx-cloud start-ci-run --distribute-on="5 linux-medium-js" --stop-agents-after="e2e-ci"

For more information about how Nx can improve your CI pipeline, check out one of these detailed tutorials:

• Circle CI with Nx
• GitHub Actions with Nx

Learn More

Learn more about the advantages of Nx in the following guides:

• Using Cypress for e2e tests
• Using Jest for unit tests
• Computation Caching
• Rebuilding and Retesting What is Affected
• Integrate with Editors
• Advanced Angular Micro Frontends with Dynamic Module Federation

From Nx Console

Nx Console no longer supports the Angular CLI. Angular CLI users will receive a notice, asking if they want to switch to Nx. When you click this button, we’ll run the nx init command to set up the Nx CLI, allowing for cached builds, and for you to share this cache with your teammates via Nx Cloud.

If you're not ready to make the change yet, you can come back to this later:

• If you're using Nx Console: open the Vs Code command palette and start typing "Convert Angular CLI to Nx Workspace".
• Regardless of using Nx Console (or your IDE): run npx nx init from the root of your project.

Once the script has run, commit the changes. Reverting this commit will effectively undo the changes made.

{% cards cols="1" mdCols="3" smCols="3" lgCols="3" %}

{% card title="Nx and the Angular CLI" description="Differences between Nx and the Angular CLI" type="documentation" url="/nx-api/angular/documents/nx-and-angular" /%}

{% card title="Multiple Angular Repositories to one Nx Workspace" description="Combine multiple Angular CLI workspaces into one Nx workspace" type="documentation" url="/recipes/angular/migration/angular-multiple" /%}

{% /cards %}