You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to depart from nvm by using pnpm env, however due to the way it manages Node.js versions, by pointing it with a symlink, I cannot work on two different projects with different Node.js version requirements at the same time, because the minute I change it, it changes globally, since it modifies where the symbolic link points to.
With nvm I can work at the same time in different projects with different Node.js version requirement as nvm stores the folder to use, which points to the proper version, on an environment variable:
Currently I cannot make the full switch to pnpm due to this fact. It would be nice to change this so we can use a single tool to manage packages and versions of Node.js.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I tried to depart from
nvm
by usingpnpm env
, however due to the way it manages Node.js versions, by pointing it with a symlink, I cannot work on two different projects with different Node.js version requirements at the same time, because the minute I change it, it changes globally, since it modifies where the symbolic link points to.With
nvm
I can work at the same time in different projects with different Node.js version requirement asnvm
stores the folder to use, which points to the proper version, on an environment variable:Currently I cannot make the full switch to
pnpm
due to this fact. It would be nice to change this so we can use a single tool to manage packages and versions of Node.js.Beta Was this translation helpful? Give feedback.
All reactions