pnpm ls equivalent for Turborepo

[maschwenk]

Which project is this feature idea for?

Turborepo

Describe the feature you'd like to request

pnpm has trouble understanding that lockfile changes can affect packages even if the package source code does not change pnpm/pnpm#4420

From my understanding of this issue, Turborepo can understand that relationship #3250

I'd like to lean on Turbo as the canonical "change detector"

Unfortunately, Turborepo requires all tasks to have a pacakge.json script associated with them. This would require us to either:

1. Setup a "dummy" script for each package that is a no-op but will allow us to navigate the DAG
2. Add a build script to scripts that don't really have a build step, just to ensure it's always included

Describe the solution you'd like

More generally, it would be nice to have a way to understand Turbo's view of the DAG divorced from any particular task.

Describe alternatives you've considered

Not sure

[ArnaudRinquin]

Wouldn't the --dry argument cover your case?

[arlyon]

I have run into this as well, wanting to get information about packages in the context of the repo rather than in the context of a particular task. --dry would help if every package happens to share a common task (such as typechecking ... 😏) but I agree that assuming that wouldn't always make sense. I will feed this back and get a timeline.

Thanks for taking the time to open an issue.

[maschwenk]

Wouldn't the --dry argument cover your case?

Using dry requires that every package in the repo has the script in question. I'd like to use turbo as a replacement for my use of pnpm ls. As mentioned above, pnpm is not a clever about change detection in certain situations, whereas Turborepo can be.