node/nvm-windows
1
0
Fork 0
mirror of https://github.com/coreybutler/nvm-windows.git synced 2025-09-11 05:29:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Corey Butler
2016-11-03 15:07:52 -05:00
committed by GitHub
parent 8a673b24b4
commit 2e183a1a6c
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@@ -104,9 +104,8 @@ just good practice.
## What's the big difference? ## What's the big difference?
First and foremost, this version of nvm has no dependency on node. It's written in [Go](https://golang.org/), which is a much more structured First and foremost, this version of nvm has no dependency on node. It's written in [Go](https://golang.org/), which is a much more structured
approach than hacking around a limited `.bat` file. It does not rely on having an existing node installation. Plus, should the need arise, Go approach than hacking around a limited `.bat` file. It does not rely on having an existing node installation. Go
offers potential for creating a Mac/Linux version on the same code base with a substanially easier migration path than converting a bunch of offers the ability to create a Mac/Linux version on the same code base. In fact, this is already underway.
batch to shell logic. `bat > sh, it crazy, right?`
The control mechanism is also quite different. There are two general ways to support multiple node installations with hot switching capabilities. The control mechanism is also quite different. There are two general ways to support multiple node installations with hot switching capabilities.
The first is to modify the system `PATH` any time you switch versions, or bypass it by using a `.bat` file to mimic the node executable and redirect The first is to modify the system `PATH` any time you switch versions, or bypass it by using a `.bat` file to mimic the node executable and redirect