Same here.

pnpm version:

6.24.2

Code to reproduce the issue:

pnpm up -igL

Expected behavior:

Update selected packages to the latest version.

Actual behavior:

Does nothing.

√ Choose which packages to update (Press <space> to select, <a> to toggle all, <i> to invert selection) · aws-cdk, pnpm
Already up-to-date
Progress: resolved 370, reused 369, downloaded 0, added 0, done

Debug information comes with --reporter ndjson.
pnpm-debug.log

Additional information:

• node -v prints: v14.18.1
• Windows, macOS, or Linux?: Windows (Microsoft Windows [Version 10.0.19044.1415])

Same here.

Try with pnpm v7

Try with pnpm v7

Still not woring in latest version 7.0.0-rc.9

Latest vsce version is 2.7.0

@zkochan

Yes, I could reproduce it.

This works though:

pnpm i --global vsce

It will install the latest vsce.

I think this is the same as #3720
I wrote the results of some investigations there: #3720 (comment), but I don't know if they are still relevant on pnpm v7.

I'm doing this as a workaround:

$ echo virtual-store-dir=.pnpm >> "$PNPM_HOME/global/5/.npmrc"
$ pnpm update --dir "$PNPM_HOME/global/5" --interactive --latest

You only need to run the first command once, then run the second command whenever you want to update your global packages.

Might be dangerous but it seems to work.

It worked for me, too, thanks @b0o

But I wonder if there will be a fix for this problem or a best practice.

@zkochan any update on this? I think this is an serious issue.

I use @b0o's way but it should be fixed ASAP.

I also noticed that when I update pnpm using brew, I lost all my global packages
Seems related to this

cc @zkochan (I really appreciate your hard work on pnpm, tnx mate ❤️ )

Yeah, doesn't work. Outdated sees it's outdated, but update just says it's all up to date, even with latest flag

Any updates?

Well, you can use npm-check-updates with the pnpm flag

var=$(pnpm dlx npm-check-updates -gp pnpm | grep -i "pnpm -g add")
eval "$var"

I'm so glad it's not just me. I was pouring over the documentation trying to figure out what I wasn't understanding.

This is the same for me. pnpm up -giL as well as pnpm up -gL do so as if they're doing work: They seem to resolve the deps, and they even download something, but this never results in an upgrade. pnpm up -g works, but not for major updates; for this, I have to kinda re-install the package (as described in #3779 (comment)).

@kytta

npm-check-updates works with pnpm and global packages. Even lets you preview and interactively select the updates.

This is seems same with version 8. What is the fix for this?

This has been fixed on v8.6.3, I'm not sure it has been fixed on v7

7.33.2 has the fix too