[rush] rush-pnpm outdated does not work

[kaiyoma]

Summary

rush-pnpm outdated does not work (prints nothing).

Repro steps

Run rush-pnpm outdated.

Expected result: Outdated dependencies

Actual result: Crickets

Details

As noted elsewhere, pnpm outdated -r -C common/temp does work, but this requires us to have pnpm installed globally. Ideally, we should be using rush for everything, and Rush should be managing pnpm for us and shielding us from that.

Standard questions

Please answer these questions to help us investigate your issue more quickly:

Question	Answer
@microsoft/rush globally installed version?	5.131.5
rushVersion from rush.json?	5.131.5
useWorkspaces from rush.json?	N/A
Operating system?	Any
Would you consider contributing a PR?	No
Node.js version (node -v)?	20.11.1

[iclanton]

I'm getting this error:

 ERR_PNPM_NO_IMPORTER_MANIFEST_FOUND  No package.json (or package.yaml, or package.json5) was found in "<repo root path>".

Looks like it may not be running in the right folder. It probably expects to run with a cwd of <repo root>/common/temp. Probably an easy fix.

[kaiyoma]

Looks like it may not be running in the right folder. It probably expects to run with a cwd of <repo root>/common/temp. Probably an easy fix.

This same approach might also fix rush-pnpm why which is similarly broken and similarly needs to run in the right directory context.

[dmichon-msft]

rush-pnpm doesn't automatically inject the -r flag, so you have to run rush-pnpm outdated -r or rush-pnpm why -r for it to work properly.

[kaiyoma]

rush-pnpm doesn't automatically inject the -r flag, so you have to run rush-pnpm outdated -r or rush-pnpm why -r for it to work properly.

Oh wow, I can't believe the solution was this simple all along. Thank you!

Do you think the -r flag should be automatically applied to these commands? If not, what about some kind of error output about the missing flag? Having the tool print nothing feels like the worst of all worlds here, since it leads to a lot of confusion.