node/nvm-windows
1
0
Fork 0
mirror of https://github.com/coreybutler/nvm-windows.git synced 2026-01-14 07:03:17 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source 
Add link to manual installation steps. Closes #577.
This commit is contained in:
Corey Butler
2020-11-04 23:12:43 -06:00
committed by GitHub
parent d2a5a6715a
commit 955a5459e5
1 changed files with 13 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
README.md
View File

@@ -11,9 +11,9 @@ Better yet, **click the "Sponsor" button** at the top of this screen.
## NOTICES
This repository has been accepted into the Github Discussions beta program. Please look for updates there. The Gitter channel will be retired in favor of this new feature.
This repository now uses [Github Discussions](https://github.com/coreybutler/nvm-windows/discussions) for updates. Sponsors also receive occasional email updates. The Gitter channel has been retired in favor of these new features.
Older notices have moved to the [notices wiki entry](https://github.com/coreybutler/nvm-windows/wiki/Notices).
Old notices have moved to the [notices wiki entry](https://github.com/coreybutler/nvm-windows/wiki/Notices).
## Common Issues & Resolutions
@@ -41,32 +41,29 @@ bleeding edge version without uninstalling the stable version of node, this util
### Installation & Upgrades
#### Uninstall existing node
#### _PREREQUISITE:_ Uninstall existing node & npm
Please note, you need to uninstall any existing versions of node.js before installing NVM for Windows. Also delete any existing nodejs installation directories (e.g., "C:\Program Files\nodejs") that might remain. NVM's generated symlink will not overwrite an existing (even empty) installation directory.
Uninstall any existing versions of Node.js before installing NVM for Windows (otherwise you'll have conflicting versions). Delete any existing Node.js installation directories (e.g., "C:\Program Files\nodejs") that might remain. NVM's generated symlink will not overwrite an existing (even empty) installation directory.
#### Uninstall existing npm
You should also delete the existing npm install location (e.g. "C:\Users\\<user>\\AppData\Roaming\npm"), so that the nvm install location will be correctly used instead. Backup the global `npmrc` config (e.g. `C:\Users\<user>\AppData\Roaming\npm\etc\npmrc`), if you have some important settings there, or copy the settings to the user config `C:\Users\<user>\.npmrc`.
Delete the existing npm install location (e.g. "C:\Users\\<user>\\AppData\Roaming\npm") to prevent global module conflicts. Remember to backup any global `npmrc` config (e.g. `C:\Users\<user>\AppData\Roaming\npm\etc\npmrc`), or copy the settings to the user config `C:\Users\<user>\.npmrc`.
#### Install nvm-windows
nvm-windows comes with an installer (and uninstaller), because getting it should be easy.
[Download the latest installer](https://github.com/coreybutler/nvm/releases) (comes with an uninstaller). There is also a manual option (see [manual installation](https://github.com/coreybutler/nvm-windows/wiki#manual-installation) in the wiki).
_If NVM4W doesn't appear to work immediately after installation, restart the terminal/powershell._
![NVM for Windows Installer](http://i.imgur.com/x8EzjSC.png)
#### Reinstall any global utilities
After install, reinstalling global utilities (e.g. gulp) will have to be done for each installed version of node:
After install, reinstalling global utilities (e.g. yarn) will have to be done for each installed version of node:
```
nvm use 4.4.0
npm install gulp-cli -g
nvm use 0.10.33
npm install gulp-cli -g
nvm use 14.0.0
npm install -g yarn
nvm use 12.0.1
npm install -g yarn
```
[Download the latest installer from the releases](https://github.com/coreybutler/nvm/releases).
![NVM for Windows Installer](http://i.imgur.com/x8EzjSC.png)
### Upgrading nvm-windows