[rush] `rush install --only .` installs all dependencies in the monorepo instead of only the dependencies in current folder/project about rushstack HOT 10 OPEN

Similar issue happens with --to. I can see how --only is not always safe, but -to should be, and installing only a subset of deps would really help reduce the time installing (specifically in CI where you don't have previously installed deps like on local )

I encountered a similar problem. After we upgraded pnpm7 to pnpm8, rush install --to projectName no longer installs the dependencies of the project specified by --to. After execution, all dependencies of the entire monorepo are installed. I would like to ask if anyone has the same problem.

rush version: 5.115.0
pnpm version: 8.15.6

If I revert back to pnpm7, everything will be normal.

from rushstack.

This seems like a recent regression. @dmichon-msft - can you take a look at this, since you refactored the project selection logic? This may have been broken by recent changes to the installation algorithm. @g-chao, @william2958 - Would you two mind taking a look at this as well, as you guys changed this logic most recently?

from rushstack.

Do we know which Rush version introduced this regression?

from rushstack.

Notice that @elenasch cited Rush 5.112.2 which is from December. Is this really a regression? Maybe it is just an edge case.

I'm actually unclear what rush install --only . is meant to do by design. Is it even valid? 🤔

from rushstack.

It might make sense to forbid the unsafe selectors (--only, --impacted-by, --impacted-by-except) for rush install and rush update.

@dmichon-msft what do you think?

from rushstack.

Similar issue happens with --to. I can see how --only is not always safe, but -to should be, and installing only a subset of deps would really help reduce the time installing (specifically in CI where you don't have previously installed deps like on local )

from rushstack.

If you run with --debug it should log the command being forwarded to pnpm. Are the --filter arguments not showing up in that command?

from rushstack.

It looks like it is there. Are there any other settings that look out of place ?

Invoking package manager: <my path>/.rush/node-v20.10.0/pnpm-8.13.1/node_modules/pnpm/bin/pnpm.cjs install --store <my path>/common/temp/pnpm-store --config.cacheDir= <my path>/common/temp/pnpm-store --config.stateDir= <my path>/common/temp/pnpm-store --no-prefer-frozen-lockfile --reporter ndjson --no-strict-peer-dependencies --config.auto-install-peers=false --config.resolutionMode=highest --config.ignoreCompatibilityDb --recursive --link-workspace-packages false --filter my-npm-package...

from rushstack.

@dmichon-msft I ran just the raw pnpm command I posted above, and it did the right thing with only installing the one project in filter (took about 5.5s) , then ran the rush install --only . and it took ~54s.

from rushstack.

@hx-dl I encountered the same problem and created an issue last year already which links to the related issue on pnpm side: #4218

from rushstack.