The nx.json file configures the Nx CLI and project defaults. The full machine readable schema is available on GitHub.

The following is an expanded example showing all options. Your nx.json will likely be much shorter.

1{ 2 "plugins": [ 3 { 4 "plugin": "@nx/eslint/plugin", 5 "options": { 6 "targetName": "lint" 7 } 8 } 9 ], 10 "parallel": 4, 11 "cacheDirectory": "tmp/my-nx-cache", 12 "defaultBase": "main", 13 "namedInputs": { 14 "default": ["{projectRoot}/**/*"], 15 "production": ["!{projectRoot}/**/*.spec.tsx"] 16 }, 17 "targetDefaults": { 18 "@nx/js:tsc": { 19 "inputs": ["production", "^production"], 20 "dependsOn": ["^build"], 21 "options": { 22 "main": "{projectRoot}/src/index.ts" 23 }, 24 "cache": true 25 }, 26 "test": { 27 "cache": true, 28 "inputs": ["default", "^production", "{workspaceRoot}/jest.preset.js"], 29 "outputs": ["{workspaceRoot}/coverage/{projectRoot}"], 30 "executor": "@nx/jest:jest" 31 } 32 }, 33 "release": { 34 "version": { 35 "generatorOptions": { 36 "currentVersionResolver": "git-tag", 37 "specifierSource": "conventional-commits" 38 } 39 }, 40 "changelog": { 41 "git": { 42 "commit": true, 43 "tag": true 44 }, 45 "workspaceChangelog": { 46 "createRelease": "github" 47 }, 48 "projectChangelogs": true 49 } 50 }, 51 "generators": { 52 "@nx/js:library": { 53 "buildable": true 54 } 55 }, 56 "extends": "nx/presets/npm.json" 57} 58


Nx plugins improve the experience of using different tools with Nx. One key feature of plugins is that they can automatically configure the way Nx runs tasks for a tool based on that tool's configuration. In order for a plugin to configure tasks for Nx, it needs to be registered in the plugins array. If a plugin has no options, it can be listed as a string. Otherwise, it should be listed as an object with a plugin property and an options property.

Every plugin behaves differently, so consult the plugin's own documentation for information about what it does. You can browse the plugin registry for available plugins.

To learn about creating your own plugin read about extending Nx.

1{ 2 "plugins": [ 3 "@my-org/graph-plugin", 4 { 5 "plugin": "@nx/eslint/plugin", 6 "options": { 7 "targetName": "lint" 8 } 9 } 10 ] 11} 12

Scope Plugins to Specific Projects

Plugins use config files to infer tasks for projects. You can specify which config files are processed by Nx plugins using the include and exclude properties in the plugin configuration object.

1{ 2 "plugins": [ 3 { 4 "plugin": "@nx/jest/plugin", 5 "include": ["packages/**/*"], // include any projects in the packages folder 6 "exclude": ["**/*-e2e/**/*"] // exclude any projects in a *-e2e folder 7 } 8 ] 9} 10

The include and exclude properties are each file glob patterns that are used to include or exclude the configuration file that the plugin is interpreting. In the example provided, the @nx/jest/plugin plugin will only infer tasks for projects where the jest.config.ts file path matches the packages/**/* glob but does not match the **/*-e2e/**/* glob.

Task Options

The following properties affect the way Nx runs tasks and can be set at the root of nx.json.

paralleldefines the max number of targets run in parallel
captureStderrdefines whether the cache captures stderr or just stdout
skipNxCachedefines whether the Nx Cache should be skipped (defaults to false)
cacheDirectorydefines where the local cache is stored (defaults to .nx/cache)
encryptionKey(when using "nx-cloud" only) defines an encryption key to support end-to-end encryption of your cloud cache. You may also provide an environment variable with the key NX_CLOUD_ENCRYPTION_KEY that contains an encryption key as its value. The Nx Cloud task runner normalizes the key length, so any length of key is acceptable
selectivelyHashTsConfigonly hash the path mapping of the active project in the tsconfig.base.json (e.g., adding/removing projects doesn't affect the hash of existing projects) (defaults to false)

You can configure parallel in nx.json, but you can also set a --parallel flag in the terminal nx run-many -t test --parallel=5.

Default Base

Tells Nx which base branch to use when calculating affected projects.

  • defaultBase defines the default base branch, defaults to main.

Target Defaults

Target defaults provide ways to set common options for a particular target in your workspace. When building your project's configuration, we merge it with up to 1 default from this map. For a given target, we look at its name and its executor. We then check target defaults looking for a configuration whose key matches any of the following:

  • `${executor}`
  • `${targetName}` (if the configuration specifies the executor, this needs to match the target's executor as well)

Target defaults matching the executor takes precedence over those matching the target name. If we find a target default for a given target, we use it as the base for that target's configuration.


When using a target name as the key of a target default, make sure all the targets with that name use the same executor or that the target defaults you're setting make sense to all targets regardless of the executor they use. Anything set in a target default will also override the configuration of tasks inferred by plugins.

Some common scenarios for this follow.

inputs & namedInputs

Named inputs defined in nx.json are merged with the named inputs defined in project level configuration. In other words, every project has a set of named inputs, and it's defined as: {...namedInputsFromNxJson, ...namedInputsFromProjectsProjectJson}.

Defining inputs for a given target would replace the set of inputs for that target name defined in nx.json. Using pseudocode inputs = projectJson.targets.build.inputs || nxJson.targetDefaults.build.inputs.

You can also define and redefine named inputs. This enables one key use case, where your nx.json can define things like this (which applies to every project):

1{ 2 "targetDefaults": { 3 "test": { 4 "inputs": ["default", "^production"] 5 } 6 } 7} 8

And projects can define their production inputs, without having to redefine the inputs for the test target.

1{ 2 "namedInputs": { 3 "production": ["default", "!{projectRoot}/**/*.test.js"] 4 } 5} 6

In this case Nx will use the right production input for each project.

Task Pipelines

Targets can depend on other targets. A common scenario is having to build dependencies of a project first before building the project. The dependsOn property in project.json can be used to define the list of dependencies of an individual target.

Often the same dependsOn configuration has to be defined for every project in the repo, and that's when defining targetDefaults in nx.json is helpful.

1{ 2 "targetDefaults": { 3 "build": { 4 "dependsOn": ["^build"] 5 } 6 } 7} 8

The configuration above is identical to adding {"dependsOn": ["^build"]} to every build target of every project.


Another target default you can configure is outputs:

1{ 2 "targetDefaults": { 3 "build": { 4 "outputs": ["{projectRoot}/custom-dist"] 5 } 6 } 7} 8

When defining any options or configurations inside of a target default, you may use the {workspaceRoot} and {projectRoot} tokens. This is useful for defining options whose values are paths.

1{ 2 "targetDefaults": { 3 "@nx/js:tsc": { 4 "options": { 5 "main": "{projectRoot}/src/index.ts" 6 }, 7 "configurations": { 8 "prod": { 9 "tsconfig": "{projectRoot}/tsconfig.prod.json" 10 } 11 }, 12 "inputs": ["prod"], 13 "outputs": ["{workspaceRoot}/{projectRoot}"] 14 }, 15 "build": { 16 "inputs": ["prod"], 17 "outputs": ["{workspaceRoot}/{projectRoot}"], 18 "cache": true 19 } 20 } 21} 22
Target Default Priority

Note that the inputs and outputs are specified on both the @nx/js:tsc and build default configurations. This is required, as when reading target defaults Nx will only ever look at one key. If there is a default configuration based on the executor used, it will be read first. If not, Nx will fall back to looking at the configuration based on target name. For instance, running nx build project will read the options from targetDefaults[@nx/js:tsc] if the target configuration for build uses the @nx/js:tsc executor. It would not read any of the configuration from the build target default configuration unless the executor does not match.


In Nx 17 and higher, caching is configured by specifying "cache": true in a target's configuration. This will tell Nx that it's ok to cache the results of a given target. For instance, if you have a target that runs tests, you can specify "cache": true in the target default configuration for test and Nx will cache the results of running tests.

1{ 2 "targetDefaults": { 3 "test": { 4 "cache": true 5 } 6 } 7} 8
Per Project Caching + Distribution

If you are using distributed task execution and disable caching for a given target, you will not be able to use distributed task execution for that target. This is because distributed task execution requires caching to be enabled. This means that the target you have disabled caching for, and any targets which depend on that target will fail the pipeline if you try to run them with Nx Agents enabled.

Executor/command options

You can configure options specific to a target's executor. As an example, if your repo has projects using the @nx/js:tsc executor, you can provide some default options as follows:

1{ 2 "targetDefaults": { 3 "@nx/js:tsc": { 4 "options": { 5 "generateExportsField": true 6 } 7 } 8 } 9} 10

You can also provide defaults for inferred targets or targets running a command using the nx:run-commands executor. As an example, if your repo has projects where all the build targets run the same vite build command, you can provide some default options as follows:

1{ 2 "targetDefaults": { 3 "build": { 4 "options": { 5 "assetsInlineLimit": 2048, 6 "assetsDir": "static/assets" 7 } 8 } 9 } 10} 11
Be careful

If multiple targets with the same name run different commands (or use different executors), do not set options in targetDefaults. Different commands would accept different options, and the target defaults will apply to all targets with the same name regardless of the command they run. If you were to provide options in targetDefaults for them, the commands that don't expect those options could throw an error.

For more details on how to pass args to the underlying command see the Pass Args to Commands recipe.


The release property in nx.json configures the nx release command. It is an optional property, as nx release is capable of working with zero config, but when present it is used to configure the versioning, changelog, and publishing phases of the release process.

For more information on how nx release works, see manage releases.

The full list of configuration options available for "release" can be found here: https://github.com/nrwl/nx/blob/master/packages/nx/src/config/nx-json.ts under NxReleaseConfiguration.


If you want to limit the projects that nx release targets, you can use the projects property in nx.json to do so. This property is either a string, or an array of strings. The strings can be project names, glob patterns, directories, tag references or anything else that is supported by the --projects filter you may know from other commands such as nx run.

1{ 2 "release": { 3 // Here we are configuring nx release to target all projects 4 // except the one called "ignore-me" 5 "projects": ["*", "!ignore-me"] 6 } 7} 8

Projects Relationship

The projectsRelationship property tells Nx whether to release projects independently or together. By default Nx will release all your projects together in lock step, which is an equivalent of "projectRelationships": "fixed". If you want to release projects independently, you can set "projectsRelationship": "independent".

1{ 2 "release": { 3 // Here we are configuring nx release to release projects 4 // independently, as opposed to the default of "fixed" 5 "projectsRelationship": "independent" 6 } 7} 8

Release Tag Pattern

Optionally override the git/release tag pattern to use. This field is the source of truth for changelog generation and release tagging, as well as for conventional commits parsing.

It supports interpolating the version as {version} and (if releasing independently or forcing project level version control system releases) the project name as {projectName} within the string.

The default "releaseTagPattern" for fixed/unified releases is: v{version}

The default "releaseTagPattern" for independent releases at the project level is: {projectName}@{version}

1{ 2 "release": { 3 // Here we are configuring nx release to use a custom release 4 // tag pattern (we have dropped the v prefix from the default) 5 "releaseTagPattern": "{version}" 6 } 7} 8


The version property configures the versioning phase of the release process. It is used to determine the next version of your projects, and update any projects that depend on them to use the new version.

Behind the scenes, the version logic is powered by an Nx generator. Out of the box Nx wires up the most widely applicable generator implementation for you, which is @nx/js:release-version provided by the @nx/js plugin.

It is therefore a common requirement to be able to tweak the options given to that generator. This can be done by configuring the release.version.generatorOptions property in nx.json:

1{ 2 "release": { 3 "version": { 4 "generatorOptions": { 5 // Here we are configuring the generator to use git tags as the 6 // source of truth for a project's current version 7 "currentVersionResolver": "git-tag", 8 // Here we are configuring the generator to use conventional 9 // commits as the source of truth for how to determine the 10 // relevant version bump for the next version 11 "specifierSource": "conventional-commits" 12 } 13 } 14 } 15} 16

For a full reference of the available options for the @nx/js:release-version generator, see the release version generator reference.


The changelog property configures the changelog phase of the release process. It is used to generate a changelog for your projects, and commit it to your repository.

There are two types of possible changelog that can be generated:

  • Workspace Changelog: A changelog that contains all changes across all projects in your workspace. This is not applicable when releasing projects independently.

  • Project Changelogs: A changelog that contains all changes for a given project.

The changelog property is used to configure both of these changelogs.

Workspace Changelog

The changelog.workspaceChangelog property configures the workspace changelog. It is used to determine if and how the workspace changelog is generated.

1{ 2 "release": { 3 "changelog": { 4 // This disables the workspace changelog 5 "workspaceChangelog": false 6 } 7 } 8} 9
1{ 2 "release": { 3 "changelog": { 4 "workspaceChangelog": { 5 // This will create a GitHub release containing the workspace 6 // changelog contents 7 "createRelease": "github", 8 // This will disable creating a workspace CHANGELOG.md file 9 "file": false 10 } 11 } 12 } 13} 14

Project Changelogs

The changelog.projectChangelogs property configures the project changelogs. It is used to determine if and how the project changelogs are generated.

1{ 2 "release": { 3 "changelog": { 4 // This enables project changelogs with the default options 5 "projectChangelogs": true 6 } 7 } 8} 9
1{ 2 "release": { 3 "changelog": { 4 "projectChangelogs": { 5 // This will create one GitHub release per project containing 6 // the project changelog contents 7 "createRelease": "github", 8 // This will disable creating any project level CHANGELOG.md 9 // files 10 "file": false 11 } 12 } 13 } 14} 15


The git property configures the automated git operations that take place as part of the release process.

1{ 2 "release": { 3 "git": { 4 // This will enable committing any changes (e.g. package.json 5 // updates, CHANGELOG.md files) to git 6 "commit": true, 7 // This will enable create a git for the overall release, or 8 // one tag per project for independent project releases 9 "tag": false 10 } 11 } 12} 13


Default generator options can be configured in nx.json. For instance, the following tells Nx to always pass --buildable=true when creating new libraries with the @nx/js plugin.

1{ 2 "generators": { 3 "@nx/js:library": { 4 "buildable": true 5 } 6 } 7} 8


Some presets use the extends property to hide some default options in a separate json file. The json file specified in the extends property is located in your node_modules folder. The Nx preset files are specified in the nx package.

Nx Cloud

There are also options for Nx Cloud that are set in the nx.json file. For instance, you authenticate with the Nx Cloud service using an nxCloudAccessToken like this:

1{ 2 "nxCloudAccessToken": "SOMETOKEN" 3} 4

For more details on configuring Nx Cloud, see the Nx Cloud Configuration Options page.