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
Identical behaviour for run and watch when run from a specific package directory, with the only difference being that watch watches
Non-goals
No response
Background
Currently, if I cd packages/a and run turbo run build, it will only use that package's build command as a target, only running its dependencies and then the build of that package.
If I cd packages/a and run turbo watch build, it suddenly looks for all build commands in the workspace, and I have to add --filter to limit the scope of the watcher.
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
-
Goals
run
andwatch
when run from a specific package directory, with the only difference being thatwatch
watchesNon-goals
No response
Background
Currently, if I
cd packages/a
and runturbo run build
, it will only use that package'sbuild
command as a target, only running its dependencies and then the build of that package.If I
cd packages/a
and runturbo watch build
, it suddenly looks for allbuild
commands in the workspace, and I have to add--filter
to limit the scope of the watcher.Proposal
Make
run
andwatch
the same.Beta Was this translation helpful? Give feedback.
All reactions