Custom Task Runner Use Cases Affected by Removal in 21

[joshlartz]

I wanted to take a minute and inform the team of the myriad of other ways we use custom task runners, beyond what the blog mentioned. I don't see how any of this will work after Nx 21.

In no particular order

• The ability to skip cache in a CI run for one off issues
• Reading our feature flag implementation and differing behavior in executors and generators
• Analytics about what executors were used, how long they took, and the like
• Checking package dependencies to ensure they conform to specific version ranges we define
• Blocking execution if critical config issues are detected
• Remote caching to S3
• Integrating Nx with Projen for scaffolding and updates to files

As you can see, a lot of it is run once/at the beginning use cases that only task runners provide. It gives us guardrails and integrations with other tools. If root tasks were a thing, it might work, but task runners are at the perfect spot to do all of these things today.

[dprothero]

This will lead to a community fork that everyone will adopt or mass exodus to something else.

[itspers]

Looks like there are not so much people care... Maybe because NX docs are so complex, that majority of people even dont understand how all this features work and dont use them.

[AlonMiz]

This change is indeed critical for businesses of all sizes. Custom task runners provide immense flexibility and adaptability, especially for teams with unique workflows or security compliance requirements.

For example, using custom runners allows us to:

1. Operate entirely within our internal network without depending on any external cloud providers.
2. Implement custom caching mechanisms tailored to our needs, ensuring optimal performance while maintaining control over data flow and security.
3. Integrate seamlessly with our existing tools and infrastructure, avoiding the need for Nx Cloud, which may not align with our security policies.

Given our constraints and compliance needs, we’re already exploring Nx alternatives. Removing custom task runners creates a significant gap that many teams, including ours, may find challenging to bridge without substantial effort or compromise. We truly hope the Nx team reconsiders this change or provides a viable alternative for self-managed setups.