Create a Sync Generator
Sync generators are generators that are used to ensure that your file system is in the correct state before a task is run or the CI process is started. From a technical perspective, a sync generator is no different from any other generator, but it has some additional performance considerations and needs to be registered in a particular way.
Create a Global Sync Generator
Global sync generators are executed when the nx sync or nx sync:check command is explicitly run by a user or in a script. They are not associated with an individual task or project and typically update root-level configuration files.
Create a sync generator the same way you would create any generator:
❯
nx g my-sync-generator --directory=tools/my-plugin/src/generators/my-sync-generator
A sync generator should be able to run without any required options, so update the schema accordingly:
1{
2 "$schema": "https://json-schema.org/schema",
3 "$id": "MySyncGenerator",
4 "title": "",
5 "type": "object",
6 "properties": {},
7 "required": []
8}
9Sync generators can optionally return an outOfSyncMessage to display to users when the sync generator needs to be run.
1import { Tree } from '@nx/devkit';
2import { SyncGeneratorResult } from 'nx/src/utils/sync-generators';
3
4export async function mySyncGenerator(
5 tree: Tree
6): Promise<SyncGeneratorResult> {
7 if (
8 !tree.exists('/legal-message.txt') ||
9 tree.read('/legal-message.txt').toString() !==
10 'This is an important legal message.'
11 ) {
12 tree.write('/legal-message.txt', 'This is an important legal message.');
13 }
14 return {
15 outOfSyncMessage: 'The legal-message.txt file needs to be created',
16 };
17}
18
19export default mySyncGenerator;
20Register a Global Sync Generator
Global sync generators are registered in the nx.json file like this:
1{
2 "sync": {
3 "globalGenerators": ["my-plugin:my-sync-generator"]
4 }
5}
6Now my-sync-generator will be executed any time the nx sync command is run.
Create a Task Sync Generator that Uses the Project Graph
Task sync generators are run before a particular task and are used to ensure that the files are in the correct state for the task to be run. The primary use case for this is to set up configuration files based on the project graph. To read from the project graph, use the createProjectGraphAsync from the @nx/devkit package. Create a generator in the same way as a global sync generator and then read the project graph like this:
1import { Tree, createProjectGraphAsync } from '@nx/devkit';
2import { SyncGeneratorResult } from 'nx/src/utils/sync-generators';
3
4export async function mySyncGenerator(
5 tree: Tree
6): Promise<SyncGeneratorResult> {
7 const projectGraph = await createProjectGraphAsync();
8 Object.values(projectGraph.nodes).forEach((project) => {
9 tree.write(
10 joinPathFragments(project.data.root, 'license.txt'),
11 `${project.name} uses the Acme Corp license.`
12 );
13 });
14 return {
15 outOfSyncMessage: 'Some projects are missing a license.txt file.',
16 };
17}
18
19export default mySyncGenerator;
20Register a Task Sync Generator
To register a generator as a sync generator for a particular task, add the generator to the syncGenerators property of the task configuration:
1{
2 "targets": {
3 "build": {
4 "syncGenerators": ["my-plugin:my-sync-generator"]
5 }
6 }
7}
8With this configuration in place, running nx build my-app will first run my-sync-generator and then run the build task. The my-sync-generator and any other task or global sync generators will be run when nx sync or nx sync:check is run.
Performance and DX Considerations
Task sync generators will block the execution of the task while they are running and both global and task sync generators will block the CI pipeline until the nx sync:check command finishes. Because of this, make sure to keep in mind the following performance tips:
- Make the generator idempotent. Running the generator multiple times in a row should have the same impact as running the generator a single time.
- Only write to the file system when a file is actually changed. Avoid reformatting files that have not been actually modified. Nx will identify the workspace as out of sync if there's any file change after the sync generator is run.
- Make sure to provide an informative
outOfSyncMessageso that developers know what to do to unblock their tasks.
Do whatever you can to make your sync generators as fast and user-friendly as possible, because users will be running them over and over again without even realizing it.