affected:lint
Lint projects affected by changes
Usage
nx affected:lint
Install nx
globally to invoke the command directly using nx
, or use npm run nx
or yarn nx
.
Examples
Run lint in parallel:
nx affected:lint --parallel --maxParallel=5
Rerun the lint target only for the projects that failed last time:
nx affected:lint --only-failed
Run the lint target for all projects:
nx affected:lint --all
Run lint for all the projects affected by changing the index.ts file:
nx affected:lint --files=libs/mylib/src/index.ts
Run lint for all the projects affected by the changes between master and HEAD (e.g., PR):
nx affected:lint --base=master --head=HEAD
Run lint for all the projects affected by the last commit on master:
nx affected:lint --base=master~1 --head=master
Options
all
All projects
base
Base of the current branch (usually master)
configuration
This is the configuration to use when performing tasks on projects
exclude
Default: ``
Exclude certain projects from being processed
files
Change the way Nx is calculating the affected command by providing directly changed files, list of files delimited by commas
head
Latest commit of the current branch (usually HEAD)
help
Show help
maxParallel
Max number of parallel processes. This flag is ignored if the parallel option is set to false
. (default: 3)
only-failed
Default: false
Isolate projects which previously failed
parallel
Parallelize the command (default: false)
runner
This is the name of the tasks runner configured in nx.json
skip-nx-cache
Default: false
Rerun the tasks even when the results are available in the cache
uncommitted
Uncommitted changes
untracked
Untracked changes
verbose
Print additional error stack trace on failure
version
Show version number