Managing Node.js versions with pnpm

This a short demo about how to use pnpm for managing Node.js versions
Related docs:
pnpm.io/cli/env#use
pnpm.io/npmrc#use-node-version

[@kalyankattamuri4941]

Thanks for sharing! Quite few things going on - nvim, fish shell, nerdtree nvim plugin, alacritty terminal, some linux distro with activities (BTW, is pretty neat) and then pnpm itself. With nvm the node version is set such that I can use it within the terminal. With this one, it is at the project level and has to be used with package.json npm scripts. Nothing wrong. Just different.

[@JuanoD_]

Hey! I was using volta until now. Time to switch all my projects, work and personal, to pnpm.

[@nivethan-me]

awesome 👍

[@tux1]

Cool, thanks!

[@neoesm]

Catch it this won't work if you don't already have a Node.js version installed

[@_adonisk]

Isn't this counter intuitive though? You want to use pnpm to manage Node.js but the idea to move forward is to use corepack to manage pnpm? How would that work if pnpm is managing the version of Node.

[@zkochan]

To me, personally, it made more sense to manage Node.js with pnpm. In the end, I want pnpm to be as stable as Git. You don’t use a version manager for Git, right? However, it looks like the other approach is more popular. In any case, even if you don’t manage the globally installed Node.js with pnpm, you can still manage it for local projects. With the use-node-version setting, you can specify which Node.js version will be used when you run scripts with pnpm.