nx-executors

To create reusable Nx executors, define the executor file structure, register it, and implement the TypeScript logic. This skill helps you scaffold executors and integrate them into your Nx workspace to standardize build tasks across multiple projects.

The ExecutorContext API provides access to the project graph and runtime context within an Nx workspace. It drives task execution across projects, allowing executors to dynamically interact with workspace configurations during build steps like linting or packaging.

Yes, you need a configured Nx workspace and familiarity with TypeScript. Access to a monorepo containing executor templates is also required to properly scaffold, register, and run custom executor targets using the `bunx nx run` command.

You validate runtime configuration for Nx executors by creating and validating JSON schemas. This skill covers schema definitions to ensure runtime config passed to your executor targets is properly typed and validated before execution.

Yes, you can reuse a standard Nx executor across multiple apps. This skill enables teams to design and implement reusable executors that standardize common build steps like linting, testing, or packaging across all projects in a TypeScript monorepo.

The best way to streamline CI/CD in an Nx monorepo is by designing and implementing reusable Nx executors. This approach standardizes build workflows, allowing teams to share common task logic across multiple applications instead of duplicating scripts.