Problems encountered during the use of nvm

Scenario: Received a new project development task, the project uses the node16+ version, before that, the company’s projects used the 14+ version, the project manager said today that you packaged the previous project (14+) for me, and encountered the following problems

 I was very puzzled. I had no problem with so many packages before, but the project suddenly couldn’t run today. I had a flash of light. It must be that I have recently upgraded the node version for a new project. Wouldn’t it be better to just cut the version?

Slap in the face, I won’t do what you think for this node version, what can you do with me?

Solution 

One, window+x to open windows PowerShell (administrator)  must select the administrator! ! !

1. Delete all node folders in a simple and rude way

Reinstall the version you want, and you can perfectly realize nvm use switching

2. Use the nvm uninstall method to uninstall the previous node version and reinstall it

Note: The node version switched by nvm must be installed after nvm installation. If it is installed before nvm installation, the switching version will not take effect 

Guess you like

Origin blog.csdn.net/weixin_47039061/article/details/131453696