What package manager are you using / does the bug impact?
npm
What operating system are you using?
Mac
Describe the Bug
The Automatic Workspace Scoping feature as it was introduced in 1.8 is no longer working on 1.10.5 and up. Downgrading back to 1.10.4 makes it work again.
Expected Behavior
When I'm inside a workspace directory and I run turbo build, I expect to only run the build for that workspace, but this no longer is happening. Instead, all the builds are being run (as if run from the top-level of the repo).
Explicitly passing --filterdoes still work, but it's no longer being auto-detected anymore.
To Reproduce
$ npm i turbo@1.10.6 # or 1.10.5
$ cd /path/to/workspace
$ turbo build
It should only run the builds for that workspace.
Instead, it runs all the builds.
What version of Turborepo are you using?
1.10.6
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Mac
Describe the Bug
The Automatic Workspace Scoping feature as it was introduced in 1.8 is no longer working on 1.10.5 and up. Downgrading back to 1.10.4 makes it work again.
Expected Behavior
When I'm inside a workspace directory and I run
turbo build
, I expect to only run the build for that workspace, but this no longer is happening. Instead, all the builds are being run (as if run from the top-level of the repo). Explicitly passing--filter
does still work, but it's no longer being auto-detected anymore.To Reproduce
It should only run the builds for that workspace. Instead, it runs all the builds.
Reproduction Repo
https://github.com/liveblocks/liveblocks