Closed ahusby closed 2 years ago
I'm not really sure what Topgrade needs to do here, especially if the problem is resolve one you upgrade pnpm
I'm not really sure what Topgrade needs to do here, especially if the problem is resolve one you upgrade pnpm
Yeah, I don't want to waste anybody's time. I run topgrade almost daily without this (or any other) issue now, so for me it's ok if you close this issue. Only I wonder if the five :+1: this issue got is because other people are bothered by this....
I'm not sure if this counts as a bug. It's not a big problem, and I think I found a solution. I love topgrade to a large degree because it Just Works out of the box. In this case it didn't and I had to start thinking and searching the web to try to find a way to run topgrade without errors.
What did you expect to happen?
Should be able to run
topgrade -v
without errors, and in this particular case have all Javascript package management tools be upgraded without errors.What actually happened?
Lots of stuff updates fine as usual, but updating of the tool pnpm fails with following output.
Additional details
The issue occured on my first attempt to run
topgrade
after I uninstalled npm which I had installed via brew for Linux. I then reinstalled npm by way of installing nvm with their recommended commandcurl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash
and then runningnvm install --lts
. I don't think topgrade ever tried to upgrade pnpm before I installed nvm, so I'm guessing I neved had pnpm installed at all before, and that it came with the installation of nvm.I found a way to run
topgrade
without errors: I ranpnpm add -g pnpm
as described in the pnpm documentation. I no longer get the error from topgrade described above.Versions in use after all steps above:
nvm --version
0.39.1npm --version
8.5.3pnpm --version
6.32.3