Configuration: package.json and nx.json

There are two main types of configuration in every Nx workspace: project configuration and the global Nx CLI configuration.

Projects can be configured in package.json (if you use npm scripts and not Nx executors) and project.json (if you use Nx executors). Both package.json and project.json files are located in each project's folder. Nx merges the two files to get each project's configuration. This guide covers the package.json case.

Project Configuration

Every npm script defined in package.json is a target you can invoke via Nx. For instance, if your project has the following package.json:

1{
2  "name": "mylib",
3  "scripts": {
4    "test": "jest",
5    "build": "tsc -p tsconfig.lib.json" // the actual command here is arbitrary
6  }
7}
8

you can invoke nx build mylib or nx test mylib without any extra configuration.

You can add Nx-specific configuration as follows:

1{
2  "name": "mylib",
3  "scripts": {
4    "test: "jest",
5    "build": "tsc -p tsconfig.lib.json" // the actual command here is arbitrary
6  },
7  "nx": {
8    "namedInputs": {
9      "default": [
10        "{projectRoot}/**/*"
11      ],
12      "prod": [
13        "!{projectRoot}/**/*.spec.tsx"
14      ]
15    },
16    "targets": {
17      "build": {
18        "inputs": ["prod", "^prod"],
19        "outputs": ["dist/libs/mylib"],
20        "dependsOn": ["^build"]
21      },
22      "test": {
23        "inputs": ["default", "^prod"],
24        "outputs": [],
25        "dependsOn": ["build"]
26      }
27    }
28  }
29}
30

inputs & namedInputs

The inputs array tells Nx what to consider to determine whether a particular invocation of a script should be a cache hit or not. There are three types of inputs:

Filesets

Examples:

• {projectRoot}/**.*.ts
• same as {fileset: "{projectRoot}/**/*.ts"}
• {workspaceRoot}/jest.config.ts
• same as {fileset: "{workspaceRoot}/jest.config.ts}

Runtime Inputs

Examples:

• {runtime: "node -v"}

Node the result value is hashed, so it is never displayed.

Env Variables

Examples:

• {env: "MY_ENV_VAR"}

Node the result value is hashed, so it is never displayed.

Named Inputs

Examples:

• inputs: ["prod"]
• same as inputs: [{input: "prod", projects: "self"}]

Often the same glob will appear in many places (e.g., prod fileset will exclude spec files for all projects). Because keeping them in sync is error-prone, we recommend defining named inputs, which you can then reference in all of those places.

Using ^

Examples:

• inputs: ["^prod"]
• same as inputs: [{input: "prod", projects: "dependencies"}]

Similar to dependsOn, the "^" symbols means "dependencies". This is a very important idea, so let's illustrate it with an example.

1"test": {
2  "inputs": [ "default", "^prod" ]
3}
4

The configuration above means that the test target depends on all source files of a given project and only prod sources (non-test sources) of its dependencies. In other words, it treats test sources as private.

outputs

"outputs": ["dist/libs/mylib"] tells Nx where the build target is going to create file artifacts. The provided value is actually the default, so we can omit it in this case. "outputs": [] tells Nx that the test target doesn't create any artifacts on disk.

This configuration is usually not needed. Nx comes with reasonable defaults (imported in nx.json) which implement the configuration above.

dependsOn

Targets can depend on other targets. This is the relevant portion of the configuration file:

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

A common scenario is having to build dependencies of a project first before building the project. This is what the "dependsOn": ["^build"] property of the build target configures. It tells Nx that before it can build mylib it needs to make sure that mylib's dependencies are built as well. This doesn't mean Nx is going to rerun those builds. If the right artifacts are already in the right place, Nx will do nothing. If they aren't in the right place, but they are available in the cache, Nx will retrieve them from the cache.

Another common scenario is for a target to depend on another target of the same project. For instance, "dependsOn": ["build"] of the test target tells Nx that before it can test mylib it needs to make sure that mylib is built, which will result in mylib's dependencies being built as well.

You can also express the same configuration using:

1"build": {
2  "dependsOn": [{ "projects": "dependencies", "target": "build" }]
3},
4"test": {
5  "dependsOn": [{ "projects": "self", "target": "build" }]
6}
7

With the expanded syntax, you also have a third option available to configure how to handle the params passed to the target dependencies. You can either forward them to the dependency target, or you can ignore them (default).

1"build": {
2   // forward params passed to this target to the dependency targets
3  "dependsOn": [{ "projects": "dependencies", "target": "build", "params": "forward" }]
4},
5"test": {
6  // ignore params passed to this target, won't be forwarded to the dependency targets
7  "dependsOn": [{ "projects": "self", "target": "build", "params": "ignore" }]
8}
9"lint": {
10  // ignore params passed to this target, won't be forwarded to the dependency targets
11  "dependsOn": [{ "projects": "self", "target": "build" }]
12}
13

This configuration is usually not needed. Nx comes with reasonable defaults (imported in nx.json) which implement the configuration above.

tags

You can annotate your projects with tags as follows:

1{
2  "name": "mylib",
3  "nx": {
4    "tags": ["scope:myteam"]
5  }
6}
7

You can configure lint rules using these tags to, for instance, ensure that libraries belonging to myteam are not depended on by libraries belong to theirteam.

implicitDependencies

Nx uses powerful source-code analysis to figure out your workspace's project graph. Some dependencies cannot be deduced statically, so you can set them manually like this:

1{
2  "name": "mylib",
3  "nx": {
4    "implicitDependencies": ["anotherlib"]
5  }
6}
7

You can also remove a dependency as follows:

1{
2  "name": "mylib",
3  "nx": {
4    "implicitDependencies": ["!anotherlib"] # regardless of what Nx thinks, "mylib" doesn't depend on "anotherlib"
5  }
6}
7

Ignoring a project

Nx will add every project with a package.json file in it to its project graph. If you want to ignore a particular project, add the following to its package.json:

1{
2  "name": "mylib",
3  "nx": {
4    "ignore": true
5  }
6}
7

workspace json

The workspace.json file in the root directory is optional. It's used if you want to list the projects in your workspace explicitly instead of Nx scanning the file tree for all project.json and package.json files that match the globs specified in the workspaces property of the root package.json.

1{
2  "version": 2,
3  "projects": {
4    "myapp": "apps/myapp"
5  }
6}
7

• "version": 2 tells Nx that we are using Nx's format for the workspace.json file.
• projects is a map of project names to their locations.

CLI Configuration

The nx.json file configures the Nx CLI and project defaults.

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

1{
2  "npmScope": "happyorg",
3  "affected": {
4    "defaultBase": "main"
5  },
6  "workspaceLayout": {
7    "appsDir": "demos",
8    "libsDir": "packages"
9  },
10  "implicitDependencies": {
11    "workspace.json": "*",
12    "package.json": {
13      "dependencies": "*",
14      "devDependencies": "*"
15    },
16    "tsconfig.base.json": "*",
17    "nx.json": "*"
18  },
19  "namedInputs": {
20    "default": ["{projectRoot}/**/*"],
21    "prod": ["!{projectRoot}/**/*.spec.tsx"]
22  },
23  "targetDefaults": {
24    "build": {
25      "inputs": ["prod", "^prod"],
26      "dependsOn": ["^build"]
27    }
28  },
29  "cli": {
30    "defaultCollection": "@nrwl/js"
31  },
32  "generators": {
33    "@nrwl/js:library": {
34      "buildable": true
35    }
36  },
37  "tasksRunnerOptions": {
38    "default": {
39      "runner": "nx/tasks-runners/default",
40      "options": {
41        "cacheableOperations": ["build", "lint", "test", "e2e"]
42      }
43    }
44  }
45}
46

NPM Scope

Tells Nx what prefix to use when generating library imports.

Affected

Tells Nx which branch and HEAD to use when calculating affected projects.

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

Workspace Layout

You can add a workspaceLayout property to modify where libraries and apps are located.

1{
2  "workspaceLayout": {
3    "appsDir": "demos",
4    "libsDir": "packages"
5  }
6}
7

These settings would store apps in /demos/ and libraries in /packages/. The paths specified are relative to the workspace root.

Files & Implicit Dependencies

Nx performs advanced source-code analysis to figure out the project graph of the workspace. So when you make a change, Nx can deduce what can be broken by this change. Some dependencies between projects and shared files cannot be inferred statically. You can configure those using implicitDependencies.

1{
2  "implicitDependencies": {
3    "workspace.json": "*",
4    "package.json": {
5      "dependencies": "*",
6      "devDependencies": {
7        "mypackage": ["mylib"]
8      },
9      "scripts": {
10        "check:*": "*"
11      }
12    },
13    "globalFile": ["myapp"],
14    "styles/**/*.css": ["myapp"]
15  }
16}
17

In the example above:

• Changing workspace.json affects every project.
• Changing the dependencies property in package.json affects every project.
• Changing the mypackage property in package.json only affects mylib.
• Changing any of the custom check scripts in package.json affects every project.
• Changing globalFile only affects myapp.
• Changing any CSS file inside the styles directory only affects myapp.

inputs & namedInputs

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

Defining inputs for a given target would replace the set of inputs for that target name defined in nx.json. Using pseudocode inputs = packageJson.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"test": {
2  "inputs": [
3    "default",
4    "^prod"
5  ]
6}
7

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

1{
2  "name": "parent",
3  "scripts": {
4    "build": "...",
5    "test": "..."
6  },
7  "dependencies": {...},
8  "nx": {
9    "namedInputs": {
10      "prod": [
11        "!{projectRoot}/**/*.test.js",
12        "{workspacRoot}/jest.config.js"
13      ]
14    }
15  }
16}
17

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

Target Defaults

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 package.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

CLI Options

The following command generates a new library: nx g @nrwl/js:lib mylib. After setting the defaultCollectionproperty, the lib is generated without mentioning the plugin name: nx g lib mylib.

1{
2  "cli": {
3    "defaultCollection": "@nrwl/js"
4  }
5}
6

Generators

Default generator options are configured in nx.json as well. For instance, the following tells Nx to always pass --buildable=true when creating new libraries.

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

Tasks Runner Options

A task is an invocation of a target.

Tasks runners are invoked when you run nx test, nx build, nx run-many, nx affected, and so on. The tasks runner named "default" is used by default. Specify a different one like this nx run-many --target=build --all --runner=another.

Tasks runners can accept different options. The following are the options supported by "nx/tasks-runners/default" and "@nrwl/nx-cloud".

runtimeCacheInputs are set as follows:

1{
2  "tasksRunnerOptions": {
3    "default": {
4      "runner": "nx/tasks-runners/default",
5      "options": {
6        "cacheableOperations": ["build", "lint", "test", "e2e"],
7        "runtimeCacheInputs": ["node -v"]
8      }
9    }
10  }
11}
12

You can configure parallel in nx.json, but you can also pass them in the terminal nx run-many --target=test --parallel=5.

.nxignore

You may optionally add an .nxignore file to the root. This file is used to specify files in your workspace that should be completely ignored by Nx.

The syntax is the same as a .gitignore file.

When a file is specified in the .nxignore file:

1. Changes to that file are not taken into account in the affected calculations.
2. Even if the file is outside an app or library, nx workspace-lint won't warn about it.