docs(misc): replace angular.io links with angular.dev (#25831)

[Angular.dev](https://angular.dev/) is now the new home for Angular
developers as mentioned in the [Angular 18 release blog
post](https://blog.angular.dev/angular-v18-is-now-available-e79d5ac0affe).

<!-- Please make sure you have read the submission guidelines before
posting an PR -->
<!--
https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr
-->

<!-- Please make sure that your commit message follows our format -->
<!-- Example: `fix(nx): must begin with lowercase` -->

## Current Behavior
<!-- This is the behavior we have today -->

## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->

## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->
<!-- Fixes NXP-759 -->

Fixes #

Author: leosvelperez

docs/blog/2023-12-20-nx-17-2-release.md

@@ -109,7 +109,7 @@ nx release version patch --project=my-project
 
 ![](/blog/images/2023-12-20/bodyimg2.webp)
 
-[Angular](https://angular.dev/) is in the middle of [a HUGE renaissance](https://blog.angular.io/introducing-angular-v17-4d7033312e4b), between their new logo, new docs site, and introduction of some awesome features like Signals.
+[Angular](https://angular.dev/) is in the middle of [a HUGE renaissance](https://blog.angular.dev/introducing-angular-v17-4d7033312e4b), between their new logo, new docs site, and introduction of some awesome features like Signals.
 
 Nx is here to support the transition! Nx has always been a great fit for Angular, and now supports Angular 17 as well as NgRx 17.
 

docs/generated/packages/angular/documents/angular-nx-version-matrix.md

@@ -1,6 +1,6 @@
 # Nx and Angular Versions
 
-The latest version of Nx supports the [actively supported versions of Angular (current and LTS versions)](https://angular.io/guide/releases#actively-supported-versions). Workspaces in any of those versions are recommended to use the latest version of Nx to benefit from all the new features and fixes.
+The latest version of Nx supports the [actively supported versions of Angular (current and LTS versions)](https://angular.dev/reference/releases#actively-supported-versions). Workspaces in any of those versions are recommended to use the latest version of Nx to benefit from all the new features and fixes.
 
 {% callout type="note" title="Older Nx and Angular versions" %}
 The support for multiple versions of Angular in the latest version of Nx was added in **v15.7.0** and started by supporting Angular v14 and v15. If your workspace is in an older version of Angular or you can't update to the latest version of Nx for some reason, please have a look at the next section to know which version of Nx to use.
@@ -34,4 +34,4 @@ We provide a recommended version, and it is usually the latest minor version of
 | ^9.0.0          | **9.6.0**                      | 8.12.4 <= 9.6.0                        |
 | ^8.0.0          | **8.12.2**                     | 8.7.0 <= 8.12.2                        |
 
-Additionally, you can check the supported versions of Node and Typescript for the version of Angular you are using in the [Angular docs](https://angular.io/guide/versions#actively-supported-versions).
+Additionally, you can check the supported versions of Node and Typescript for the version of Angular you are using in the [Angular docs](https://angular.dev/reference/versions#actively-supported-versions).

docs/generated/packages/angular/documents/nx-and-angular.md

@@ -52,7 +52,7 @@ Here's a quick side-by-side overview comparing the features between the Angular
 
 \* You can setup a monorepo with the Angular CLI creating buildable Angular ng-packagr projects, but the DX is not as optimized compared to what you'd get with Nx.
 
-\*\* The Angular CLI has a [caching mechanism](https://angular.io/cli/cache) which persists the Webpack/ESBuild/"TS incremental build info" cache to disk. Nx leverages that cache as well but in addition adds a more powerful process-level caching on top that is framework agnostic.
+\*\* The Angular CLI has a [caching mechanism](https://angular.dev/cli/cache) which persists the Webpack/ESBuild/"TS incremental build info" cache to disk. Nx leverages that cache as well but in addition adds a more powerful process-level caching on top that is framework agnostic.
 
 {% /callout %}
 

docs/generated/packages/angular/executors/application.json

@@ -172,7 +172,7 @@
         "description": "Automatically clear the terminal screen during rebuilds. _Note: this is only supported in Angular versions >= 17.2.0_."
       },
       "optimization": {
-        "description": "Enables optimization of the build output. Including minification of scripts and styles, tree-shaking, dead-code elimination, inlining of critical CSS and fonts inlining. For more information, see https://angular.io/guide/workspace-config#optimization-configuration.",
+        "description": "Enables optimization of the build output. Including minification of scripts and styles, tree-shaking, dead-code elimination, inlining of critical CSS and fonts inlining. For more information, see https://angular.dev/reference/configs/workspace-config#optimization-configuration.",
         "default": true,
         "x-user-analytics": "ep.ng_optimization",
         "oneOf": [
@@ -307,7 +307,7 @@
         "default": true
       },
       "sourceMap": {
-        "description": "Output source maps for scripts and styles. For more information, see https://angular.io/guide/workspace-config#source-map-configuration.",
+        "description": "Output source maps for scripts and styles. For more information, see https://angular.dev/reference/configs/workspace-config#source-map-configuration.",
         "default": false,
         "oneOf": [
           {

docs/generated/packages/angular/executors/browser-esbuild.json

@@ -168,7 +168,7 @@
         "default": []
       },
       "optimization": {
-        "description": "Enables optimization of the build output. Including minification of scripts and styles, tree-shaking, dead-code elimination, inlining of critical CSS and fonts inlining. For more information, see https://angular.io/guide/workspace-config#optimization-configuration.",
+        "description": "Enables optimization of the build output. Including minification of scripts and styles, tree-shaking, dead-code elimination, inlining of critical CSS and fonts inlining. For more information, see https://angular.dev/reference/configs/workspace-config#optimization-configuration.",
         "default": true,
         "x-user-analytics": "ep.ng_optimization",
         "oneOf": [
@@ -259,7 +259,7 @@
         "default": true
       },
       "sourceMap": {
-        "description": "Output source maps for scripts and styles. For more information, see https://angular.io/guide/workspace-config#source-map-configuration.",
+        "description": "Output source maps for scripts and styles. For more information, see https://angular.dev/reference/configs/workspace-config#source-map-configuration.",
         "default": false,
         "oneOf": [
           {

docs/generated/packages/angular/executors/dev-server.json

@@ -36,7 +36,7 @@
       },
       "proxyConfig": {
         "type": "string",
-        "description": "Proxy configuration file. For more information, see https://angular.io/guide/build#proxying-to-a-backend-server."
+        "description": "Proxy configuration file. For more information, see https://angular.dev/tools/cli/serve#proxying-to-a-backend-server."
       },
       "ssl": {
         "type": "boolean",

docs/generated/packages/angular/executors/module-federation-dev-server.json

@@ -34,7 +34,7 @@
       },
       "proxyConfig": {
         "type": "string",
-        "description": "Proxy configuration file. For more information, see https://angular.io/guide/build#proxying-to-a-backend-server."
+        "description": "Proxy configuration file. For more information, see https://angular.dev/tools/cli/serve#proxying-to-a-backend-server."
       },
       "ssl": {
         "type": "boolean",

docs/generated/packages/angular/executors/webpack-browser.json

@@ -182,7 +182,7 @@
         "additionalProperties": false
       },
       "optimization": {
-        "description": "Enables optimization of the build output. Including minification of scripts and styles, tree-shaking, dead-code elimination, inlining of critical CSS and fonts inlining. For more information, see https://angular.io/guide/workspace-config#optimization-configuration.",
+        "description": "Enables optimization of the build output. Including minification of scripts and styles, tree-shaking, dead-code elimination, inlining of critical CSS and fonts inlining. For more information, see https://angular.dev/reference/configs/workspace-config#optimization-configuration.",
         "x-user-analytics": 16,
         "default": true,
         "oneOf": [
@@ -296,7 +296,7 @@
         "default": true
       },
       "sourceMap": {
-        "description": "Output source maps for scripts and styles. For more information, see https://angular.io/guide/workspace-config#source-map-configuration.",
+        "description": "Output source maps for scripts and styles. For more information, see https://angular.dev/reference/configs/workspace-config#source-map-configuration.",
         "default": false,
         "oneOf": [
           {

docs/generated/packages/angular/executors/webpack-server.json

@@ -77,7 +77,7 @@
         "additionalProperties": false
       },
       "optimization": {
-        "description": "Enables optimization of the build output. Including minification of scripts and styles, tree-shaking and dead-code elimination. For more information, see https://angular.io/guide/workspace-config#optimization-configuration.",
+        "description": "Enables optimization of the build output. Including minification of scripts and styles, tree-shaking and dead-code elimination. For more information, see https://angular.dev/reference/configs/workspace-config#optimization-configuration.",
         "default": true,
         "x-user-analytics": "ep.ng_optimization",
         "oneOf": [
@@ -148,7 +148,7 @@
         "description": "The path where style resources will be placed, relative to outputPath."
       },
       "sourceMap": {
-        "description": "Output source maps for scripts and styles. For more information, see https://angular.io/guide/workspace-config#source-map-configuration.",
+        "description": "Output source maps for scripts and styles. For more information, see https://angular.dev/reference/configs/workspace-config#source-map-configuration.",
         "default": false,
         "oneOf": [
           {

docs/generated/packages/angular/generators/add-linting.json

@@ -11,7 +11,7 @@
     "examples": [
       {
         "command": "nx g @nx/angular:add-linting --prefix=cool --projectName=cool-lib --projectRoot=libs/cool-lib",
-        "description": "Adds ESLint with Angular-specific rules for an existing project named `cool-lib` with the [prefix](https://angular.io/guide/styleguide#style-02-07) `cool`"
+        "description": "Adds ESLint with Angular-specific rules for an existing project named `cool-lib` with the [prefix](https://angular.dev/style-guide#style-02-07) `cool`"
       }
     ],
     "properties": {

docs/shared/deprecated/angular-schematics-builders.md

@@ -1,6 +1,6 @@
 # Angular Schematics and Builders
 
-As of Nx 17, official Nx plugins no longer export [schematics](https://angular.io/guide/schematics) and [builders](https://angular.io/guide/cli-builder) that can be directly consumed by the Angular CLI. Since Angular CLI users are not a large portion of Nx's user base, it made sense to stop maintaining that code.
+As of Nx 17, official Nx plugins no longer export [schematics](https://angular.dev/tools/cli/schematics) and [builders](https://angular.dev/tools/cli/cli-builder) that can be directly consumed by the Angular CLI. Since Angular CLI users are not a large portion of Nx's user base, it made sense to stop maintaining that code.
 
 Currently, the Angular CLI can only run its own schematics and builders. The Nx CLI is still able to directly run any schematics or builders created for the Angular CLI as well as Nx's own generators and executors. The only thing that has changed is that Nx is no longer taking the extra step of converting our own code into a format that the Angular CLI recognizes.
 

docs/shared/guides/nx-and-angular-cli.md

@@ -52,7 +52,7 @@ Here's a quick side-by-side overview comparing the features between the Angular
 
 \* You can setup a monorepo with the Angular CLI creating buildable Angular ng-packagr projects, but the DX is not as optimized compared to what you'd get with Nx.
 
-\*\* The Angular CLI has a [caching mechanism](https://angular.io/cli/cache) which persists the Webpack/ESBuild/"TS incremental build info" cache to disk. Nx leverages that cache as well but in addition adds a more powerful process-level caching on top that is framework agnostic.
+\*\* The Angular CLI has a [caching mechanism](https://angular.dev/cli/cache) which persists the Webpack/ESBuild/"TS incremental build info" cache to disk. Nx leverages that cache as well but in addition adds a more powerful process-level caching on top that is framework agnostic.
 
 {% /callout %}
 

docs/shared/guides/using-tailwind-css-with-angular-projects.md

@@ -1,7 +1,7 @@
 # Using Tailwind CSS with Angular projects
 
 The purpose of this page is to cover how to use and configure [Tailwind CSS](https://tailwindcss.com/)
-with [Angular](https://angular.io/) projects. It shows the different options available to set it up in existing projects
+with [Angular](https://angular.dev/) projects. It shows the different options available to set it up in existing projects
 or new projects, and it also contains a set of our recommended setups for using Tailwind CSS in different scenarios that
 can be found on an Nx workspace.
 

docs/shared/packages/angular/angular-nx-version-matrix.md

@@ -1,6 +1,6 @@
 # Nx and Angular Versions
 
-The latest version of Nx supports the [actively supported versions of Angular (current and LTS versions)](https://angular.io/guide/releases#actively-supported-versions). Workspaces in any of those versions are recommended to use the latest version of Nx to benefit from all the new features and fixes.
+The latest version of Nx supports the [actively supported versions of Angular (current and LTS versions)](https://angular.dev/reference/releases#actively-supported-versions). Workspaces in any of those versions are recommended to use the latest version of Nx to benefit from all the new features and fixes.
 
 {% callout type="note" title="Older Nx and Angular versions" %}
 The support for multiple versions of Angular in the latest version of Nx was added in **v15.7.0** and started by supporting Angular v14 and v15. If your workspace is in an older version of Angular or you can't update to the latest version of Nx for some reason, please have a look at the next section to know which version of Nx to use.
@@ -34,4 +34,4 @@ We provide a recommended version, and it is usually the latest minor version of
 | ^9.0.0          | **9.6.0**                      | 8.12.4 <= 9.6.0                        |
 | ^8.0.0          | **8.12.2**                     | 8.7.0 <= 8.12.2                        |
 
-Additionally, you can check the supported versions of Node and Typescript for the version of Angular you are using in the [Angular docs](https://angular.io/guide/versions#actively-supported-versions).
+Additionally, you can check the supported versions of Node and Typescript for the version of Angular you are using in the [Angular docs](https://angular.dev/reference/versions#actively-supported-versions).

docs/shared/recipes/storybook/angular-configuring-styles.md

@@ -9,7 +9,7 @@ description: This document explains how to configure styles and preprocessor opt
 This documentation page contains information about the [Storybook plugin](/nx-api/storybook), specifically regarding [Angular projects that are using Storybook](/recipes/storybook/overview-angular).
 {% /callout %}
 
-Angular supports including extra entry-point files for styles. Also, in case you use Sass, you can add extra base paths that will be checked for imports. In your project's `project.json` file you can use the `styles` and `stylePreprocessorOptions` properties in your `storybook` and `build-storybook` target `options`, as you would in your Storybook or your Angular configurations. If your project is an application, you can add these extra options in your `build` target. Your `storybook` and `build-storybook` `browserTarget` are going to be pointing to the `build` target, so they will pick up these styles from there. Check out the [Angular Workspace Configuration](https://angular.io/guide/workspace-config#styles-and-scripts-configuration) documentation for more information. You can also check the [official Storybook for Angular documentation](https://storybook.js.org/docs/angular/configure/styling-and-css) on working with styles and CSS.
+Angular supports including extra entry-point files for styles. Also, in case you use Sass, you can add extra base paths that will be checked for imports. In your project's `project.json` file you can use the `styles` and `stylePreprocessorOptions` properties in your `storybook` and `build-storybook` target `options`, as you would in your Storybook or your Angular configurations. If your project is an application, you can add these extra options in your `build` target. Your `storybook` and `build-storybook` `browserTarget` are going to be pointing to the `build` target, so they will pick up these styles from there. Check out the [Angular Workspace Configuration](https://angular.dev/reference/configs/workspace-config#styles-and-scripts-configuration) documentation for more information. You can also check the [official Storybook for Angular documentation](https://storybook.js.org/docs/angular/configure/styling-and-css) on working with styles and CSS.
 
 Your Storybook targets in your `project.json` will look like this:
 

docs/shared/recipes/storybook/plugin-angular.md

@@ -148,7 +148,7 @@ Notice the interaction test on the second story, inside the `play` function. Thi
 You will notice that `browserTarget` is specified for the `storybook` and `build-storybook` targets, much like it is done for `serve` or other targets. Angular needs the `browserTarget` for Storybook in order to know which configuration to use for the build. If your project is buildable (it has a `build` target, and uses the main Angular builder - `@angular-devkit/build-angular:browser`, `@angular-devkit/build-angular:application` or `@angular-devkit/build-angular:browser-esbuild`) the `browserTarget` for Storybook will use the `build` target, if it's not buildable (or is using another Angular builder) it will use the `build-storybook` target.
 You do not have to do anything manually. Nx will create the configuration for you. Even if you are migrating from an older version of Nx, Nx will make sure to change your `package.json` Storybook targets to match the new schema.
 
-You can read more about the `browserTarget` in the [official Angular documentation](https://angular.io/cli/serve).
+You can read more about the `browserTarget` in the [official Angular documentation](https://angular.dev/cli/serve).
 
 Your Storybook targets in your `project.json` (or if you run `nx show project my-project --web`) will look like this:
 

packages/angular/src/builders/dev-server/schema.json

@@ -36,7 +36,7 @@
     },
     "proxyConfig": {
       "type": "string",
-      "description": "Proxy configuration file. For more information, see https://angular.io/guide/build#proxying-to-a-backend-server."
+      "description": "Proxy configuration file. For more information, see https://angular.dev/tools/cli/serve#proxying-to-a-backend-server."
     },
     "ssl": {
       "type": "boolean",

packages/angular/src/builders/webpack-browser/schema.json

@@ -153,7 +153,7 @@
       "additionalProperties": false
     },
     "optimization": {
-      "description": "Enables optimization of the build output. Including minification of scripts and styles, tree-shaking, dead-code elimination, inlining of critical CSS and fonts inlining. For more information, see https://angular.io/guide/workspace-config#optimization-configuration.",
+      "description": "Enables optimization of the build output. Including minification of scripts and styles, tree-shaking, dead-code elimination, inlining of critical CSS and fonts inlining. For more information, see https://angular.dev/reference/configs/workspace-config#optimization-configuration.",
       "x-user-analytics": 16,
       "default": true,
       "oneOf": [
@@ -242,7 +242,7 @@
       "default": true
     },
     "sourceMap": {
-      "description": "Output source maps for scripts and styles. For more information, see https://angular.io/guide/workspace-config#source-map-configuration.",
+      "description": "Output source maps for scripts and styles. For more information, see https://angular.dev/reference/configs/workspace-config#source-map-configuration.",
       "default": false,
       "oneOf": [
         {