majiayu000 Run tasks with Nx via pnpm nx (Hedgehog workspaces are pnpm-only).
For more details on any command, run it with --help (e.g. pnpm nx run-many --help, pnpm nx affected --help).
Understand which tasks can be run
You can check those via pnpm nx show project <projectname> --json, for example pnpm nx show project myapp --json. It contains a targets section which has information about targets that can be run. You can also just look at the package.json scripts or project.json targets, but you might miss out on inferred tasks by Nx plugins.
Run a single task
pnpm nx run <project>:<task>
where project is the project name defined in package.json or project.json (if present).
Run multiple tasks
pnpm nx run-many -t build test lint typecheck
You can pass a -p flag to filter to specific projects, otherwise it runs on all projects. You can also use --exclude to exclude projects, and --parallel to control the number of parallel processes (default is 3).
Examples:
pnpm nx run-many -t test -p proj1 proj2— test specific projectspnpm nx run-many -t test --projects=*-app --exclude=excluded-app— test projects matching a patternpnpm nx run-many -t test --projects=tag:api-*— test projects by tag
Run tasks for affected projects
Use pnpm nx affected to only run tasks on projects that have been changed and projects that depend on changed projects. This is especially useful in CI and for large workspaces.
pnpm nx affected -t build test lint
By default it compares against the base branch. You can customize this:
pnpm nx affected -t test --base=main --head=HEAD— compare against a specific base and headpnpm nx affected -t test --files=libs/mylib/src/index.ts— specify changed files directly
Useful flags
These flags work with run, run-many, and affected:
--skipNxCache— rerun tasks even when results are cached--verbose— print additional information such as stack traces--nxBail— stop execution after the first failed task--configuration=<name>— use a specific configuration (e.g.production)