Nathan Hammond

@tm1000 https://github.com/vercel/turbo/blob/6a0228125cafbbceed53ff17a7b25259422df568/cli/internal/config/config_file.go#L138 https://github.com/vercel/turbo/blob/6a0228125cafbbceed53ff17a7b25259422df568/cli/internal/config/config_file.go#L180-L182 So, we need to make sure that it is not read in from `/.turbo/config.json`.

Hey y'all, we're aware of this limitation. If you look very closely you'll see that we throw an error message about this support. We look forward to bringing support for...

@chris-olszewski This was an intentional change introduced in https://github.com/vercel/turbo/pull/1275/commits/494b89423c189781d0d0a5fae5382bfcdd3b300c We need to make sure that we don't regress #1265.

/cc @mehulkar

@mehulkar I suspect we could just reorder the cycle check.

Hey y'all, we're aware of this limitation. If you look very closely you'll see that we throw an error message about this support. We look forward to bringing support for...

So, the `--scope` flag for `prune` and the `--scope` flag for `run` are intentionally distinct. My apologies for the confusion. `--scope` for `prune` is _not_ deprecated, and it's using that...

Indeed, this is not a Turborepo bug. We do not contribute to this in any way. The specific behavior for where things are installed are based upon the package manager's...

Hey everybody, unfortunately I'm going to have to close this. It is actually not possible for us to infer which package manager to use without taking input from one of...

@timneutkens Is this considered public API? Nextra may not be the only tool that uses this API. (Opened here for discussion reasons as to where to make the change.)