Complete Nx plugin development toolkit: create custom generators, executors, and extend Nx workspaces with reusable automation
93
94%
Does it follow best practices?
Impact
92%
1.00xAverage score across 5 eval scenarios
Passed
No known issues
Use this reference when implementing executor behavior with Nx context metadata.
context.root: workspace root path.context.projectName: active project name.context.targetName: current target key.context.configurationName: active configuration, if provided.context.projectsConfigurations: full project graph metadata.import type { ExecutorContext } from "@nx/devkit";
export default async (_options: { outputPath: string }, context: ExecutorContext) => {
const project = context.projectName ?? "unknown-project";
const target = context.targetName ?? "unknown-target";
console.log(`Running ${project}:${target}`);
return { success: true };
};context.root.??) to avoid brittle assumptions.