Nx comes with dedicated documentation for each framework:

Workspace Generators

Workspace generators provide a way to automate many tasks you regularly perform as part of your development workflow. Whether it is scaffolding out components, features, or ensuring libraries are generated and structured in a certain way, generators help you standardize these tasks in a consistent, and predictable manner. Nx provides tooling around creating, and running custom generators from within your workspace. This guide shows you how to create, run, and customize workspace generators within your Nx workspace.

Creating a workspace generator

Use the Nx CLI to generate the initial files needed for your workspace generator.

nx generate @nrwl/workspace:workspace-generator my-generator

After the command is finished, the workspace generator is created under the tools/generators folder.

happynrwl/
├── apps/
├── libs/
├── tools/
│   ├── generators
│   |   └── my-generator/
│   |   |    ├── index.ts
│   |   |    └── schema.json
├── nx.json
├── package.json
└── tsconfig.base.json

The index.ts provides an entry point to the generator. The file contains a function that is called to perform manipulations on a tree that represents the file system. The schema.json provides a description of the generator, available options, validation information, and default values.

The initial generator function creates a library.

1import { Tree, formatFiles, installPackagesTask } from '@nrwl/devkit';
2import { libraryGenerator } from '@nrwl/workspace';
3
4export default async function (tree: Tree, schema: any) {
5  await libraryGenerator(tree, { name: schema.name });
6  await formatFiles(tree);
7  return () => {
8    installPackagesTask(tree);
9  };
10}

To invoke other generators, import the entry point function and run it against the tree tree. async/await can be used to make code with Promises read like procedural code. The generator function may return a callback function that is executed after changes to the file system have been applied.

In the schema.json file for your generator, the name is provided as a default option. The cli property is set to nx to signal that this is a generator that uses @nrwl/devkit and not @angular-devkit.

1{
2  "cli": "nx",
3  "id": "test",
4  "type": "object",
5  "properties": {
6    "name": {
7      "type": "string",
8      "description": "Library name",
9      "$default": {
10        "$source": "argv",
11        "index": 0
12      }
13    }
14  },
15  "required": ["name"]
16}

The $default object is used to read arguments from the command-line that are passed to the generator. The first argument passed to this schematic is used as the name property.

Running a workspace generator

To run a generator, invoke the nx workspace-generator command with the name of the generator.

nx workspace-generator my-generator mylib

Running a workspace schematic created with @angular-devkit

Generators that are created using the @angular-devkit are called schematics. Workspace schematics that have been created with the @angular-devkit will omit the "cli": "nx" property in schema.json. Nx will recognize this and correctly run the schematic using the same command as an @nrwl/devkit generator.

nx workspace-generator my-schematic mylib

The command is also aliased to the previous workspace-schematic command, so this still works:

nx workspace-schematic my-schematic mylib

Debugging Workspace generators

With Visual Studio Code

  1. Open the Command Palette and choose Debug: Create JavaScript Debug Terminal. This will open a terminal with debugging enabled.
  2. Set breakpoints in your code
  3. Run nx workspace-generator my-generator in the debug terminal.

Workspace Generator Utilities

The @nrwl/devkit package provides many utility functions that can be used in schematics to help with modifying files, reading and updating configuration files, and working with an Abstract Syntax Tree (AST).