-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Adds nx sync to command reference - Updates nx.json reference - Update project configuration reference - Adds a sync generators concept page - Adds a Register a Sync Generator recipe under Extending Nx Recipes --------- Co-authored-by: James Henry <[email protected]>
1 parent
b6140d4
commit 4517d9f
Showing
18 changed files
with
514 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
title: 'sync:check - CLI command' | ||
description: 'Check that no changes are required after running all sync generators.' | ||
--- | ||
|
||
# sync:check | ||
|
||
Check that no changes are required after running all sync generators. | ||
|
||
## Usage | ||
|
||
```shell | ||
nx sync:check | ||
``` | ||
|
||
Install `nx` globally to invoke the command directly using `nx`, or use `npx nx`, `yarn nx`, or `pnpm nx`. | ||
|
||
## Options | ||
|
||
| Option | Type | Description | | ||
| ----------- | ------- | ---------------------------------------------------------------------- | | ||
| `--help` | boolean | Show help. | | ||
| `--verbose` | boolean | Prints additional information about the commands (e.g., stack traces). | | ||
| `--version` | boolean | Show version number. | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
title: 'sync - CLI command' | ||
description: 'Sync the workspace files by running all the sync generators.' | ||
--- | ||
|
||
# sync | ||
|
||
Sync the workspace files by running all the sync generators. | ||
|
||
## Usage | ||
|
||
```shell | ||
nx sync | ||
``` | ||
|
||
Install `nx` globally to invoke the command directly using `nx`, or use `npx nx`, `yarn nx`, or `pnpm nx`. | ||
|
||
## Options | ||
|
||
| Option | Type | Description | | ||
| ----------- | ------- | ---------------------------------------------------------------------- | | ||
| `--help` | boolean | Show help. | | ||
| `--verbose` | boolean | Prints additional information about the commands (e.g., stack traces). | | ||
| `--version` | boolean | Show version number. | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
title: 'sync:check - CLI command' | ||
description: 'Check that no changes are required after running all sync generators.' | ||
--- | ||
|
||
# sync:check | ||
|
||
Check that no changes are required after running all sync generators. | ||
|
||
## Usage | ||
|
||
```shell | ||
nx sync:check | ||
``` | ||
|
||
Install `nx` globally to invoke the command directly using `nx`, or use `npx nx`, `yarn nx`, or `pnpm nx`. | ||
|
||
## Options | ||
|
||
| Option | Type | Description | | ||
| ----------- | ------- | ---------------------------------------------------------------------- | | ||
| `--help` | boolean | Show help. | | ||
| `--verbose` | boolean | Prints additional information about the commands (e.g., stack traces). | | ||
| `--version` | boolean | Show version number. | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
title: 'sync - CLI command' | ||
description: 'Sync the workspace files by running all the sync generators.' | ||
--- | ||
|
||
# sync | ||
|
||
Sync the workspace files by running all the sync generators. | ||
|
||
## Usage | ||
|
||
```shell | ||
nx sync | ||
``` | ||
|
||
Install `nx` globally to invoke the command directly using `nx`, or use `npx nx`, `yarn nx`, or `pnpm nx`. | ||
|
||
## Options | ||
|
||
| Option | Type | Description | | ||
| ----------- | ------- | ---------------------------------------------------------------------- | | ||
| `--help` | boolean | Show help. | | ||
| `--verbose` | boolean | Prints additional information about the commands (e.g., stack traces). | | ||
| `--version` | boolean | Show version number. | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
# Sync Generators | ||
|
||
In Nx 19.8, you can use sync generators to ensure that your repository is maintained in a correct state. One specific application is to use the project graph to update files. These can be global configuration files or scripts, or at the task level to ensure that files are in sync before a task is run. | ||
|
||
Sync Generator Examples: | ||
|
||
- Update a custom CI script with binning strategies based on the current project graph | ||
- Update TypeScript config files with project references based on the current project graph | ||
- Ensure code is formatted in a specific way before CI is run | ||
|
||
## Task Sync Generators | ||
|
||
Sync generators can be associated with a particular task. Nx will use the sync generator to ensure that code is correctly configured before running the task. | ||
Nx does this in different ways, depending on whether the task is being run on a developer machine or in CI. | ||
|
||
On a developer machine, the sync generator is run in `--dry-run` mode and if files would be changed by the generator, the user is prompted to run the generator or skip it. This prompt can be disabled by setting the `sync.applyChanges` property to `true` or `false` in the `nx.json` file. | ||
|
||
In CI, the sync generator is run in `--dry-run` mode and if files would be changed by the generator, the task fails with an error provided by the sync generator. The sync generator can be skipped in CI by passing the `--skip-sync` flag when executing the task or you can skip an individual sync generator by adding that generator to the `sync.disabledTaskSyncGenerators` in `nx.json`. | ||
|
||
Task sync generators can be thought of like the `dependsOn` property, but for generators instead of task dependencies. | ||
|
||
To [register a generator](/extending-nx/recipes/create-sync-generator) as a sync generator for a particular task, add the generator to the `syncGenerators` property of the task configuration. | ||
|
||
## Global Sync Generators | ||
|
||
Global sync generators are not associated with a particular task and are executed only when the `nx sync` or `nx sync:check` command is explicitly run. They are [registered](/extending-nx/recipes/create-sync-generator) in the `nx.json` file with the `sync.globalGenerators` property. | ||
|
||
## Sync the Project Graph and the File System | ||
|
||
Nx processes the file system in order to [create the project graph](/features/explore-graph) which is used to run tasks in the correct order and determine project dependencies. Sync generators allow you to also go the other direction and use the project graph to update the file system. | ||
|
||
{% side-by-side %} | ||
|
||
```{% fileName="File System" %} | ||
└─ myorg | ||
├─ apps | ||
│ ├─ app1 | ||
│ └─ app1 | ||
├─ libs | ||
│ └─ lib | ||
├─ nx.json | ||
└─ package.json | ||
``` | ||
|
||
{% graph title="Project Graph" height="200px" type="project" jsonFile="shared/mental-model/three-projects.json" %} | ||
{% /graph %} | ||
{% /side-by-side %} | ||
|
||
The ability to update the file system from the project graph makes it possible to use the Nx project graph to change the behavior of other tools that are not part of the Nx ecosystem. | ||
|
||
## Run `nx sync:check` in CI | ||
|
||
Task sync generators are executed whenever their task is run, but global sync generators need to be triggered manually with `nx sync`. In order to effectively use sync generators, make sure to add `nx sync:check` to the beginning of your CI scripts so that CI can fail quickly if the code is out of sync. It is also helpful to run `nx sync` in a pre-commit or pre-push Git hook to encourage developers to commit code that is already in sync. |
135 changes: 135 additions & 0 deletions
135
docs/shared/recipes/generators/create-sync-generator.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,135 @@ | ||
# 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](/extending-nx/recipes/local-generators): | ||
|
||
```shell | ||
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: | ||
|
||
```jsonc {% fileName="tools/my-plugin/src/generators/my-sync-generator/schema.json" %} | ||
{ | ||
"$schema": "https://json-schema.org/schema", | ||
"$id": "MySyncGenerator", | ||
"title": "", | ||
"type": "object", | ||
"properties": {}, | ||
"required": [] | ||
} | ||
``` | ||
|
||
Sync generators can optionally return an `outOfSyncMessage` to display to users when the sync generator needs to be run. | ||
|
||
```ts {% fileName="tools/my-plugin/src/generators/my-sync-generator/my-sync-generator.ts" %} | ||
import { Tree } from '@nx/devkit'; | ||
import { SyncGeneratorResult } from 'nx/src/utils/sync-generators'; | ||
|
||
export async function mySyncGenerator( | ||
tree: Tree | ||
): Promise<SyncGeneratorResult> { | ||
if ( | ||
!tree.exists('/legal-message.txt') || | ||
tree.read('/legal-message.txt').toString() !== | ||
'This is an important legal message.' | ||
) { | ||
tree.write('/legal-message.txt', 'This is an important legal message.'); | ||
} | ||
return { | ||
outOfSyncMessage: 'The legal-message.txt file needs to be created', | ||
}; | ||
} | ||
|
||
export default mySyncGenerator; | ||
``` | ||
|
||
### Register a Global Sync Generator | ||
|
||
Global sync generators are registered in the `nx.json` file like this: | ||
|
||
```jsonc {% fileName="project.json" %} | ||
{ | ||
"sync": { | ||
"globalGenerators": ["my-plugin:my-sync-generator"] | ||
} | ||
} | ||
``` | ||
|
||
Now `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`](/nx-api/devkit/documents/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: | ||
|
||
```ts {% fileName="tools/my-plugin/src/generators/my-sync-generator/my-sync-generator.ts" %} | ||
import { Tree, createProjectGraphAsync } from '@nx/devkit'; | ||
import { SyncGeneratorResult } from 'nx/src/utils/sync-generators'; | ||
|
||
export async function mySyncGenerator( | ||
tree: Tree | ||
): Promise<SyncGeneratorResult> { | ||
const projectGraph = await createProjectGraphAsync(); | ||
Object.values(projectGraph.nodes).forEach((project) => { | ||
tree.write( | ||
joinPathFragments(project.data.root, 'license.txt'), | ||
`${project.name} uses the Acme Corp license.` | ||
); | ||
}); | ||
return { | ||
outOfSyncMessage: 'Some projects are missing a license.txt file.', | ||
}; | ||
} | ||
|
||
export default mySyncGenerator; | ||
``` | ||
|
||
### Register 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: | ||
|
||
{% tabs %} | ||
{% tab label="package.json" %} | ||
|
||
```jsonc {% fileName="apps/my-app/package.json" %} | ||
{ | ||
"targets": { | ||
"build": { | ||
"syncGenerators": ["my-plugin:my-sync-generator"] | ||
} | ||
} | ||
} | ||
``` | ||
|
||
{% /tab %} | ||
{% tab label="project.json" %} | ||
|
||
```jsonc {% fileName="apps/my-app/project.json" %} | ||
{ | ||
"targets": { | ||
"build": { | ||
"syncGenerators": ["my-plugin:my-sync-generator"] | ||
} | ||
} | ||
} | ||
``` | ||
|
||
{% /tab %} | ||
{% /tabs %} | ||
|
||
With 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 `outOfSyncMessage` so 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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters