Skip to content
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

--latest argument doesn't work in interactive mode #2997

Open
kidonng opened this issue Nov 24, 2020 · 8 comments
Open

--latest argument doesn't work in interactive mode #2997

kidonng opened this issue Nov 24, 2020 · 8 comments
Projects

Comments

@kidonng
Copy link

kidonng commented Nov 24, 2020

pnpm version:

5.13.4

Code to reproduce the issue:

Install any package that is not the latest, and try to update it through pnpm update --latest -i.

Update: Looks like this bug only affects global packages, so please refer to the screencast for reproducing:

Screencast:

Screen.Recording.2020-11-24.at.13.18.56.mov

Expected behavior:

The package is updated.

Actual behavior:

pnpm reports Already up-to-date.

Additional information:

  • node -v prints: v15.2.1
  • Windows, macOS, or Linux?: macOS 11.0.1
@ShaneLee-9
Copy link

me too

@kidonng
Copy link
Author

kidonng commented Feb 8, 2021

Seems like this also happens on similiar commands, such as pnpm install-completion:

Screen.Recording.2021-02-08.at.18.55.32.mov

@hooray
Copy link

hooray commented Sep 1, 2021

same problem in pnpm@6.14.5

@Cansiny0320
Copy link

any fix on this issue?

@zkochan zkochan added this to Priority in Status Dec 8, 2021
@silver886
Copy link

Same here,

node: v14.18.1
pnpm: 6.24.2
OS: Microsoft Windows [Version 10.0.19044.1415]

and

node: v17.2.0
pnpm: 6.24.2
OS: macOS 10.15.7 (19H1519)

And it seems like #3779 is the same.

@zkochan
Copy link
Member

zkochan commented Feb 10, 2022

Hopefully this will be fixed in pnpm v7, which will use a more deterministic global folder location.

@kidonng
Copy link
Author

kidonng commented Mar 11, 2022

@zkochan No luck :(

$ pnpm --version
7.0.0-alpha.4
$ pnpm add vercel@21.0.0 -g
Packages: +97
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Packages are hard linked from the content-addressable store to the virtual store.
  Content-addressable store is at: /home/codespace/.pnpm-store/v3
  Virtual store is at:             node_modules/.pnpm
Downloading registry.npmjs.org/typescript/3.9.3: 9.58 MB/9.58 MB, done
Progress: resolved 97, reused 0, downloaded 97, added 97, done
node_modules/.pnpm/vercel@21.0.0/node_modules/vercel: Running preinstall script, done in 52ms

/home/codespace/.local/share/pnpm/global-packages/5:
+ vercel 21.0.0 (24.0.0 is available)
$ pnpm up -i -g --latest
✔ Choose which packages to update (Press <space> to select, <a> to toggle all, <i> to invert selection) · vercel

Already up-to-date
Progress: resolved 1, reused 1, downloaded 0, added 0, done

@silver886
Copy link

Version 7.1.9 is still the same :(

image

And looks like #3720 has similar symptoms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Priority
Status
Priority
Development

No branches or pull requests

6 participants