You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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
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.
Beta Was this translation helpful? Give feedback.
All reactions