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
With Nx 21, custom task runners have been replaced by the new preTasksExecution and postTasksExecution hooks.
In our monorepo, part of our workflow relied on nx run-many triggering post-task actions after each individual task, allowing us to track intermediate results. However, with the new lifecycle hooks, these are only invoked once before any tasks start and once after all tasks finish, which means we have lost the ability to react between individual task executions.
I am trying to understand the reasoning behind removing this more granular lifecycle capability from the API. Is there any chance that per-task lifecycle hooks (or a similar mechanism) might return in the future to support workflows like ours?
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
Uh oh!
There was an error while loading. Please reload this page.
-
With Nx 21, custom task runners have been replaced by the new
preTasksExecutionandpostTasksExecutionhooks.In our monorepo, part of our workflow relied on
nx run-manytriggering post-task actions after each individual task, allowing us to track intermediate results. However, with the new lifecycle hooks, these are only invoked once before any tasks start and once after all tasks finish, which means we have lost the ability to react between individual task executions.I am trying to understand the reasoning behind removing this more granular lifecycle capability from the API. Is there any chance that per-task lifecycle hooks (or a similar mechanism) might return in the future to support workflows like ours?
Beta Was this translation helpful? Give feedback.
All reactions