Build fluency in extending and optimizing Nx monorepos.
0 / 5 completed
1 / 5
At standup, a dev wants to extend Nx with framework-specific capabilities. What packages provide these?
Nx plugins extend the workspace with generators, executors, and inferred tasks for specific tech stacks. They package conventions so teams don't wire everything by hand. Plugins are the main extension mechanism in Nx.
2 / 5
During a design review, the team wants to scaffold new libraries consistently. Which plugin capability fits?
A generator scaffolds or modifies code and config in a consistent way, like creating a new library. Plugins ship generators you run with nx generate. They enforce conventions across the monorepo.
3 / 5
In a code review, a dev defines how a project is built or tested. Which plugin construct is this?
An executor implements a runnable target such as build, test, or serve for a project. You invoke it via nx run project:target. Executors abstract the underlying tool commands.
4 / 5
An incident report shows CI rebuilding everything on a tiny change. Which Nx feature limits work to what changed?
Nx affected commands use the project graph to run tasks only for projects impacted by a change. This dramatically cuts CI time versus rebuilding everything. It is a core efficiency feature of Nx monorepos.
5 / 5
During a PR review, a dev wants build artifacts shared across machines and CI. Which Nx feature provides this?
Nx remote cache shares computation results across developers and CI runners, so a task built once is reused everywhere. It builds on Nx's local caching keyed by inputs. This avoids redundant work across the team.