Building Angular Apps with the Nx Standalone Projects Setup

In this tutorial you'll learn how to use Angular with Nx in a "standalone" (non-monorepo) setup. Not to be confused with the "Angular Standalone API", a standalone project in Nx is a non-monorepo setup where you have a single application at the root level. This setup is very similar to what the Angular CLI gives you.

What are you going to learn?

  • how to create a new standalone (single-project) Nx workspace setup for Angular
  • how to run a single task (i.e. serve your app) or run multiple tasks in parallel
  • how to leverage code generators to scaffold components
  • how to modularize your codebase and impose architectural constraints for better maintainability
Looking for Angular monorepos?

Note, this tutorial sets up a repo with a single application at the root level that breaks out its code into libraries to add structure. If you are looking for an Angular monorepo setup then check out our Angular monorepo tutorial.

Warm Up

Here's the source code of the final result for this tutorial.

Example repository/nrwl/nx-recipes/tree/main/angular-standalone

StackBlitz

Open in Stackblitz

Also, if you prefer learning with a video, join Juri and walk through the tutorial, step by step together.

Creating a new Angular App

Create a new Angular application with the following command:

~❯

npx create-nx-workspace@latest myngapp --preset=angular-standalone

✔ Would you like to use Standalone Components in your application? · Yes ✔ Would you like to add routing? · Yes ✔ Default stylesheet format · css ✔ Enable distributed caching to make your CI faster · Yes

You get asked a few questions that help Nx preconfigure your new Angular application. These include

  • Angular specific questions, such as whether you want to have the router set up for you, whether to use the Angular Standalone API and which stylesheet format to use
  • General Nx questions, such as whether to enable distributed caching with Nx Cloud. Nx comes with built-in local caching. If you want to benefit from this cache in CI, you can enable distributed caching which will set up Nx Cloud. This is also a prerequisite for enabling distributed task execution.

For the sake of this tutorial, let's respond to all the questions with "yes".

The create-nx-workspace command generates the following structure:

└─ myngapp ├─ .vscode │ └─ extensions.json ├─ e2e │ ├─ ... │ ├─ project.json │ ├─ src │ │ ├─ e2e │ │ │ └─ app.cy.ts │ │ ├─ ... │ └─ tsconfig.json ├─ src │ ├─ app │ │ ├─ app.component.css │ │ ├─ app.component.html │ │ ├─ app.component.spec.ts │ │ ├─ app.component.ts │ │ ├─ app.config.ts │ │ ├─ app.routes.ts │ │ └─ nx-welcome.component.ts │ ├─ assets │ ├─ favicon.ico │ ├─ index.html │ ├─ main.ts │ ├─ styles.css │ └─ test-setup.ts ├─ jest.config.ts ├─ jest.preset.js ├─ nx.json ├─ package-lock.json ├─ package.json ├─ project.json ├─ README.md ├─ tsconfig.app.json ├─ tsconfig.editor.json ├─ tsconfig.json └─ tsconfig.spec.json

The setup includes..

  • a new Angular application at the root of the Nx workspace (src/app)
  • a Cypress based set of e2e tests (e2e/)
  • Prettier preconfigured
  • ESLint & Angular ESLint preconfigured
  • Jest preconfigured

Compared to the Angular CLI, you might notice the addition of an nx.json file and the absence of an angular.json file. Instead of the angular.json file there is a project.json file. Each file is described below:

FileDescription
nx.jsonThis is where we can fine-tune how Nx works, define the cacheable operations, our task pipelines as well as defaults for the Nx generators. Find more details in the reference docs.
project.jsonNx uses this file to define targets that can be run, similar to how the Angular CLI uses the angular.json file. If you're familiar with the Angular CLI you should have no difficulty navigating the project.json file. If you're curious how the two compare, you can learn more in the Nx and Angular CLI comparision article. The project-configuration documentation page has more details on how to use the project.json file.

Serving the App

The most common tasks are already defined in the package.json file:

package.json
{ "name": "myngapp", "scripts": { "start": "nx serve", "build": "nx build", "test": "nx test" } ... }

To serve your new Angular application, just run: npm start. Alternatively you can directly use Nx by using

nx serve

Your application should be served at http://localhost:4200.

Nx uses the following syntax to run tasks:

Syntax for Running Tasks in Nx

All targets, such as serve, build, test or your custom ones, are defined in the project.json file.

{ "name": "myngapp", ... "targets": { "serve": { ... }, "build": { ... }, "preview": { ... }, "test": { ... }, "lint": { ... }, "serve-static": { ... }, }, }

Each target contains a configuration object that tells Nx how to run that target.

{ "name": "myngapp", ... "targets": { "serve": { "executor": "@angular-devkit/build-angular:dev-server", "configurations": { "production": { "browserTarget": "myngapp:build:production" }, "development": { "browserTarget": "myngapp:build:development" } }, "defaultConfiguration": "development" }, ... }, }

The most critical parts are:

  • executor - This corresponds to the builder property in an Angular CLI workspace. You can use Angular builders or executors from Nx plugins.
  • options - these are additional properties and flags passed to the executor function to customize it

Learn more about how to run tasks with Nx.

Testing and Linting - Running Multiple Tasks

Our current setup not only has targets for serving and building the Angular application, but also has targets for unit testing, e2e testing and linting. Again, these are defined in the project.json file. We can use the same syntax as before to run these tasks:

nx test # runs tests using Jest nx lint # runs linting with ESLint nx e2e e2e # runs e2e tests with Cypress

More conveniently, we can also run them in parallel using the following syntax:

myngapp❯

nx run-many -t test lint e2e

✔ nx run e2e:lint (1s) ✔ nx run myngapp:lint (1s) ✔ nx run myngapp:test (2s) ✔ nx run e2e:e2e (6s) —————————————————————————————————————————————————————— > NX Successfully ran targets test, lint, e2e for 2 projects (8s)

Caching

One thing to highlight is that Nx is able to cache the tasks you run.

Note that all of these targets are automatically cached by Nx. If you re-run a single one or all of them again, you'll see that the task completes immediately. In addition, (as can be seen in the output example below) there will be a note that a matching cache result was found and therefore the task was not run again.

myngapp❯

nx run-many -t test lint e2e

✔ nx run myngapp:lint [existing outputs match the cache, left as is] ✔ nx run e2e:lint [existing outputs match the cache, left as is] ✔ nx run myngapp:test [existing outputs match the cache, left as is] ✔ nx run e2e:e2e [existing outputs match the cache, left as is] ——————————————————————————————————————————————————————— > NX Successfully ran targets test, lint, e2e for 2 projects (143ms) Nx read the output from the cache instead of running the command for 4 out of 4 tasks.

Not all tasks might be cacheable though. You can configure cacheableOperations in the nx.json file. You can also learn more about how caching works.

Creating New Components

Similar to the Angular CLI, Nx comes with code generation abilities. What the Angular CLI calls "Schematics", Nx calls "Generators".

Generators allow you to easily scaffold code, configuration or entire projects. To see what capabilities the @nx/angular plugin ships with, run the following command and inspect the output:

myngapp❯

npx nx list @nx/angular

> NX Capabilities in @nx/angular: > NX Capabilities in @nx/angular: GENERATORS add-linting : Adds linting configuration to an Angular project. application : Creates an Angular application. component : Generate an Angular Component. ... library : Creates an Angular library. library-secondary-entry-point : Creates a secondary entry point for an Angular publishable library. remote : Generate a Remote Angular Module Federation Application. move : Moves an Angular application or library to another folder within the workspace and updates the project configuration. convert-to-with-mf : Converts an old micro frontend configuration... host : Generate a Host Angular Module Federation Application. ng-add : Migrates an Angular CLI workspace to Nx or adds the Angular plugin to an Nx workspace. ngrx : Adds NgRx support to an application or library. scam-to-standalone : Convert an existing Single Component Angular Module (SCAM) to a Standalone Component. scam : Generate a component with an accompanying Single Component Angular Module (SCAM). scam-directive : Generate a directive with an accompanying Single Component Angular Module (SCAM). scam-pipe : Generate a pipe with an accompanying Single Component Angular Module (SCAM). setup-mf : Generate a Module Federation configuration for a given Angular application. setup-ssr : Generate Angular Universal (SSR) setup for an Angular application. setup-tailwind : Configures Tailwind CSS for an application or a buildable/publishable library. stories : Creates stories/specs for all components declared in a project. storybook-configuration : Adds Storybook configuration to a project. cypress-component-configuration : Setup Cypress component testing for a project. web-worker : Creates a Web Worker. directive : Generate an Angular directive. ngrx-feature-store : Adds an NgRx Feature Store to an application or library. ngrx-root-store : Adds an NgRx Root Store to an application. pipe : Generate an Angular Pipe EXECUTORS/BUILDERS/ delegate-build : Delegates the build to a different target while supporting incremental builds. ...
Nx 15 and lower use @nrwl/ instead of @nx/
Prefer a more visual UI?

If you prefer a more integrated experience, you can install the "Nx Console" extension for your code editor. It has support for VSCode, IntelliJ and ships a LSP for Vim. Nx Console provides autocompletion support in Nx configuration files and has UIs for browsing and running generators.

More info can be found in the integrate with editors article.

Run the following command to generate a new "hello-world" component. Note how we append --dry-run to first check the output.

myngapp❯

npx nx g @nx/angular:component hello-world --standalone --dry-run

> NX Generating @nx/angular:component CREATE src/app/hello-world/hello-world.component.css CREATE src/app/hello-world/hello-world.component.html CREATE src/app/hello-world/hello-world.component.spec.ts CREATE src/app/hello-world/hello-world.component.ts NOTE: The "dryRun" flag means no changes were made.
Nx 15 and lower use @nrwl/ instead of @nx/

As you can see it generates a new component in the app/hello-world/ folder. If you want to actually run the generator, remove the --dry-run flag.

src/app/hello-world/hello-world.component.ts
import { Component } from '@angular/core'; import { CommonModule } from '@angular/common'; @Component({ selector: 'myngapp-hello-world', standalone: true, imports: [CommonModule], templateUrl: './hello-world.component.html', styleUrls: ['./hello-world.component.css'], }) export class HelloWorldComponent {}

Building the App for Deployment

If you're ready and want to ship your application, you can build it using

myngapp❯

npx nx build

> nx run myngapp:build:production ✔ Browser application bundle generation complete. ✔ Copying assets complete. ✔ Index html generation complete. Initial Chunk Files | Names | Raw Size | Estimated Transfer Size main.afa99fe9f64fbdd9.js | main | 193.58 kB | 51.57 kB polyfills.1acfd3f58d94d542.js | polyfills | 32.98 kB | 10.66 kB runtime.37059233034b21c2.js | runtime | 892 bytes | 515 bytes styles.ef46db3751d8e999.css | styles | 0 bytes | - | Initial Total | 227.44 kB | 62.73 kB Build at: 2023-05-23T14:00:31.981Z - Hash: 9086e92ce0bfefca - Time: 5228ms —————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————— > NX Successfully ran target build for project myngapp (7s)

All the required files will be placed in the dist/myngapp folder and can be deployed to your favorite hosting provider.

You're ready to go!

In the previous sections you learned about the basics of using Nx, running tasks and navigating an Nx workspace. You're ready to ship features now!

But there's more to learn. You have two possibilities here:

Modularizing your Angular App with Local Libraries

When you develop your Angular application, usually all your logic sits in the app folder. Ideally separated by various folder names which represent your "domains". As your app grows, this becomes more and more monolithic though.

The following structure is a common example of this kind of monolithic code organization:

└─ myngapp ├─ ... ├─ src │ ├─ app │ │ ├─ products │ │ ├─ cart │ │ ├─ ui │ │ ├─ ... │ │ └─ app.component.ts │ ├─ ... │ └─ main.ts ├─ ... ├─ package.json ├─ ...

Nx allows you to separate this logic into "local libraries". The main benefits include

  • better separation of concerns
  • better reusability
  • more explicit "APIs" between your "domain areas"
  • better scalability in CI by enabling independent test/lint/build commands for each library
  • better scalability in your teams by allowing different teams to work on separate libraries

Creating Local Libraries

Let's assume our domain areas include products, orders and some more generic design system components, called ui. We can generate a new library for each of these areas using the Angular library generator:

nx g @nx/angular:library products --directory=modules --standalone --simpleName nx g @nx/angular:library orders --directory=modules --standalone --simpleName nx g @nx/angular:library ui --directory=modules/shared --standalone --simpleName
Nx 15 and lower use @nrwl/ instead of @nx/

Note how we use the --directory flag to place the libraries into a subfolder. You can choose whatever folder structure you like, even keep all of them at the root-level.

Running the above commands should lead to the following directory structure:

└─ myngapp ├─ ... ├─ e2e/ ├─ modules │ ├─ products │ │ ├─ .eslintrc.json │ │ ├─ README.md │ │ ├─ jest.config.ts │ │ ├─ project.json │ │ ├─ src │ │ │ ├─ index.ts │ │ │ ├─ lib │ │ │ │ └─ products │ │ │ │ ├─ products.component.css │ │ │ │ ├─ products.component.html │ │ │ │ ├─ products.component.spec.ts │ │ │ │ └─ products.component.ts │ │ │ └─ test-setup.ts │ │ ├─ tsconfig.json │ │ ├─ tsconfig.lib.json │ │ └─ tsconfig.spec.json │ ├─ orders │ │ ├─ ... │ │ ├─ src │ │ │ ├─ index.ts │ │ │ ├─ lib │ │ │ │ └─ orders │ │ │ │ ├─ ... │ │ │ │ └─ orders.component.ts │ │ ├─ ... │ └─ shared │ └─ ui │ ├─ ... │ ├─ src │ │ ├─ index.ts │ │ ├─ lib │ │ │ └─ ui │ │ │ ├─ ... │ │ │ └─ ui.component.ts │ └─ ... ├─ ... ├─ src │ ├─ app │ │ ├─ ... │ │ ├─ app.component.ts │ ├─ ... ├─ ...

Each of these libraries

  • has its own project.json file with corresponding targets you can run (e.g. running tests for just orders: nx test modules-orders)
  • has a name based on the --directory flag, e.g. modules-orders; you can find the name in the corresponding project.json file
  • has a dedicated index.ts file which is the "public API" of the library
  • is mapped in the tsconfig.base.json at the root of the workspace

Importing Libraries into the Angular Application

All libraries that we generate automatically have aliases created in the root-level tsconfig.base.json.

tsconfig.base.json
{ "compilerOptions": { ... "paths": { "@myngapp/modules/products": ["modules/products/src/index.ts"], "@myngapp/modules/orders": ["modules/orders/src/index.ts"], "@myngapp/modules/shared/ui": ["modules/shared/ui/src/index.ts"] }, ... }, }

Hence we can easily import them into other libraries and our Angular application. For example: let's use our existing ProductsComponent in modules/products/src/lib/products/:

import { Component } from '@angular/core'; import { CommonModule } from '@angular/common'; @Component({ selector: 'myngapp-products', standalone: true, imports: [CommonModule], templateUrl: './products.component.html', styleUrls: ['./products.component.css'], }) export class ProductsComponent {}

Make sure the ProductsComponent is exported via the index.ts file of our products library (which it should already be). The modules/products/src/index.ts file is the public API for the modules-products library with the rest of the workspace. Only export what's really necessary to be usable outside the library itself.

modules/products/src/index.ts
export * from './lib/products/products.component';

We're ready to import it into our main application now. If you opted into generating a router configuration when setting up the Nx workspace initially, you should have an app.routes.ts file in your app folder. If not, create it and configure the Angular router.

Configure the routing as follows:

src/app/app.routes.ts
import { Route } from '@angular/router'; import { NxWelcomeComponent } from './nx-welcome.component'; export const appRoutes: Route[] = [ { path: '', component: NxWelcomeComponent, pathMatch: 'full', }, { path: 'products', loadComponent: () => import('@myngapp/modules/products').then((m) => m.ProductsComponent), }, ];

As part of this step, we should also remove the NxWelcomeComponent from the AppComponent.imports declaration so that it is just loaded over the routing mechanism. The app.component.html should just have the <router-outlet> left:

src/app/app.component.html
<router-outlet></router-outlet>

If you now navigate to http://localhost:4200/products you should see the ProductsComponent being rendered.

Browser screenshot of navigating to the products route

Let's do the same process for our orders library. Import the OrdersComponent into the app.routes.ts:

src/app/app.routes.ts
import { Route } from '@angular/router'; import { NxWelcomeComponent } from './nx-welcome.component'; export const appRoutes: Route[] = [ { path: '', component: NxWelcomeComponent, pathMatch: 'full', }, { path: 'products', loadComponent: () => import('@myngapp/modules/products').then((m) => m.ProductsComponent), }, { path: 'orders', loadComponent: () => import('@myngapp/modules/orders').then((m) => m.OrdersComponent), }, ];

Similarly, navigating to http://localhost:4200/orders should now render the OrdersComponent.

A couple of notes:

  • both the ProductsComponent and OrdersComponent are lazy loaded
  • you could go even further and configure routes within the libraries and only import and attach those routes to the application routing mechanism.

Visualizing your Project Structure

Nx automatically detects the dependencies between the various parts of your workspace and builds a project graph. This graph is used by Nx to perform various optimizations such as determining the correct order of execution when running tasks like nx build, identifying affected projects and more. Interestingly you can also visualize it.

Just run:

nx graph

You should be able to see something similar to the following in your browser (hint: click the "Show all projects" button).

Notice how modules-shared-ui is not yet connected to anything because we didn't import it in any of our projects. Also the arrows to modules-orders and modules-products are dashed because we're using lazy imports.

Exercise for you: change the codebase so that modules-shared-ui is used by modules-orders and modules-products. Note: you need to restart the nx graph command to update the graph visualization or run the CLI command with the --watch flag.

Imposing Constraints with Module Boundary Rules

Once you modularize your codebase you want to make sure that the modules are not coupled to each other in an uncontrolled way. Here are some examples of how we might want to guard our small demo workspace:

  • we might want to allow modules-orders to import from modules-shared-ui but not the other way around
  • we might want to allow modules-orders to import from modules-products but not the other way around
  • we might want to allow all libraries to import the modules-shared-ui components, but not the other way around

When building these kinds of constraints you usually have two dimensions:

  • type of project: what is the type of your library. Example: "feature" library, "utility" library, "data-access" library, "ui" library (see library types)
  • scope (domain) of the project: what domain area is covered by the project. Example: "orders", "products", "shared" ... this really depends on the type of product you're developing

Nx comes with a generic mechanism that allows you to assign "tags" to projects. "tags" are arbitrary strings you can assign to a project that can be used later when defining boundaries between projects. For example, go to the project.json of your modules-orders library and assign the tags type:feature and scope:orders to it.

modules/orders/project.json
{ ... "tags": ["type:feature", "scope:orders"], ... }

Then go to the project.json of your modules-products library and assign the tags type:feature and scope:products to it.

modules/products/project.json
{ ... "tags": ["type:feature", "scope:products"], ... }

Finally, go to the project.json of the modules-shared-ui library and assign the tags type:ui and scope:shared to it.

modules/shared/ui/project.json
{ ... "tags": ["type:ui", "scope:shared"], ... }

Notice how we assign scope:shared to our UI library because it is intended to be used throughout the workspace.

Next, let's come up with a set of rules based on these tags:

  • type:feature should be able to import from type:feature and type:ui
  • type:ui should only be able to import from type:ui
  • scope:orders should be able to import from scope:orders, scope:shared and scope:products
  • scope:products should be able to import from scope:products and scope:shared

To enforce the rules, Nx ships with a custom ESLint rule. Open the .eslintrc.base.json at the root of the workspace and add the following depConstraints in the @nx/enforce-module-boundaries rule configuration:

.eslintrc.base.json
{ ... "overrides": [ { ... "rules": { "@nx/enforce-module-boundaries": [ "error", { "enforceBuildableLibDependency": true, "allow": [], "depConstraints": [ { "sourceTag": "*", "onlyDependOnLibsWithTags": ["*"] }, { "sourceTag": "type:feature", "onlyDependOnLibsWithTags": ["type:feature", "type:ui"] }, { "sourceTag": "type:ui", "onlyDependOnLibsWithTags": ["type:ui"] }, { "sourceTag": "scope:orders", "onlyDependOnLibsWithTags": [ "scope:orders", "scope:products", "scope:shared" ] }, { "sourceTag": "scope:products", "onlyDependOnLibsWithTags": ["scope:products", "scope:shared"] }, { "sourceTag": "scope:shared", "onlyDependOnLibsWithTags": ["scope:shared"] } ] } ] } }, ... ] }
Nx 15 and lower use @nrwl/ instead of @nx/

To test it, go to your modules/products/src/lib/products/products.component.ts file and import the OrderComponent from the modules-orders project:

modules/products/src/lib/products/products.component.ts
import { Component } from '@angular/core'; import { CommonModule } from '@angular/common'; // 👇 this import is not allowed import { OrdersComponent } from '@myngapp/modules/orders'; @Component({ selector: 'myngapp-products', standalone: true, imports: [CommonModule, OrdersComponent], templateUrl: './products.component.html', styleUrls: ['./products.component.css'], }) export class ProductsComponent {}

If you lint your workspace you'll get an error now:

~/workspace❯

nx run-many -t lint

✖ nx run modules-products:lint Linting "modules-products"... /Users/juri/nrwl/content/myngapp/modules/products/src/lib/products/products.component.ts 3:1 error A project tagged with "scope:products" can only depend on libs tagged with "scope:products", "scope:shared" @nx/enforce-module-boundaries ✖ 1 problem (1 error, 0 warnings) Lint errors found in the listed files. ✔ nx run modules-orders:lint (1s) ✔ nx run myngapp:lint (1s) ✔ nx run e2e:lint (682ms) ✔ nx run modules-shared-ui:lint (797ms) ————————————————————————————————————————————————————————————————————— > NX Ran target lint for 5 projects (2s) ✔ 4/5 succeeded [0 read from cache] ✖ 1/5 targets failed, including the following: - nx run modules-products:lint
Nx 15 and lower use @nrwl/ instead of @nx/

If you have the ESLint plugin installed in your IDE you should immediately see an error:

ESLint module boundary error

Learn more about how to enforce module boundaries.

Next Steps

Congrats, you made it!! You now know how to leverage the Nx standalone applications preset to build modular Angular applications.

Here's some more things you can dive into next:

Also, make sure you