New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
outdated command is inefficient #2632
Comments
We have the fastest installation, so our codebase should be able to have the fastest outdated command. There are probably just some inefficiencies that needs to be fixed. |
You might as well look at |
Try 5.2.0 |
Will do. I'll do a new comparison with |
Much better! But still 56% slower than updates. |
Maybe we can come up with some other improvements but I don't have more ideas at the moment. There is nothing special in the codebase of "updates". They use npm's package for fetching metadata. But they don't read any of the npm configs (we do). And they probably have less code, so the CLI startup is faster. Our CLI startup is pretty slow. Probably that's the reason. |
It isn't worth worrying about. 56% slower is way better than 200% slower. |
pnpm version:
5.1.8
Code to reproduce the issue:
Behavior:
I hope for
pnpm outdated
to be as fast as updates. Here's the results forpnpm outdated
vsupdates
in a project with 94 top level dependencies:updates
is >2x faster. And it uses 6x less bandwidth!Since
updates
is open source, why not just use their algorithm (with attribution of course)?Additional information:
node -v
prints: v14.3.0The text was updated successfully, but these errors were encountered: