Goals

1. able to run package manager commands/actions on individual project
2. still able to benefits running tasks with caching from turbo

Non-goals

1. running non-task at root level

Background

There are many cases you want to run something against a particular project within a monorepo.
For example, run build, run test, or add a dependency.

One way is using package manager filter feature. Using pnpm as an example, it is pnpm --filter <project> ....
The benefit of this approach is you can do pnpm --filter <project> add -D jest.
But the down side is when running pnpm --filter <project> build, turbo is not involved thus the result is not cached.

On the other hand, using turbo --filter <project> ... does not support turbo --filter <project> add -D jest.

To streamline things, I would typically add an alias at the top level, as ... --filter <project> ... is too much typing (e.g. pnpm --filter ./packages/package-a ... or pnpm --filter @repobuddy/biome ...). So I would do:

// package.json
{
  "scripts": {
    "tp": "pnpm --filter type-plus",
    // or
    "tp": "turbo --filter type-plus"
  }
}

so that I can do: nr tp build or nr tp add -D jest

Proposal

The nr tp add -D jest doesn't work with turbo.
That's what I purpose to add.

When the command is not a defined task, pass it through to the package manager.
This can be enable behind a config option.