From 1318cb1acad38cc52939139219027547fb13e3e0 Mon Sep 17 00:00:00 2001 From: Alexander Stein Date: Sat, 19 Mar 2016 17:16:39 +0300 Subject: [PATCH 1/2] [Docs] Quickly explain how to use nvm, per #1030. Briefly explain what nvm is and what it does, and how that is separate from the npm package manager, as others say the summary only shows in the Github UI. --- README.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.markdown b/README.markdown index 671a603..9affa10 100644 --- a/README.markdown +++ b/README.markdown @@ -1,5 +1,11 @@ # Node Version Manager [![Build Status](https://travis-ci.org/creationix/nvm.svg?branch=master)][3] +## Why? Node has a package manager, NPM, right? + +Yes, it does. `nvm` manages different versions of the node interpreter and core libraries. Node is powerful, but the power of the Node ecosystem is the thousands of user-contributed libraries. If you want additional libraries and tools, you use `npm` for that. + +So why `nvm`? Your operating system typically has one supported version of a programming language environment. So when developers want you to use any other version but the one installed in your operating system, you can't install these packages with `npm` because you have the wrong version of Node. With `nvm`, you have the power and flexibility to run many different versions of the Node platform simultaneously: for development, for testing, for daily use, the way you see fit. + ## Installation First you'll need to make sure your system has a c++ compiler. For OSX, XCode will work, for Ubuntu, the build-essential and libssl-dev packages work. From c7871e98122fae4e2a0deccdf82e1d16c9eda748 Mon Sep 17 00:00:00 2001 From: Alexander Stein Date: Sat, 19 Mar 2016 22:06:36 +0300 Subject: [PATCH 2/2] [Docs] Update #1030 PR with ljharb's comments. Clean up the PR with the following requests from @ljharb. - Convert spacing between sentences from one two. - Always refer to npm in lower case. --- README.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.markdown b/README.markdown index 9affa10..2ae086c 100644 --- a/README.markdown +++ b/README.markdown @@ -1,10 +1,10 @@ # Node Version Manager [![Build Status](https://travis-ci.org/creationix/nvm.svg?branch=master)][3] -## Why? Node has a package manager, NPM, right? +## Why? Node has a package manager, npm, right? -Yes, it does. `nvm` manages different versions of the node interpreter and core libraries. Node is powerful, but the power of the Node ecosystem is the thousands of user-contributed libraries. If you want additional libraries and tools, you use `npm` for that. +Yes, it does. `nvm` manages different versions of the node interpreter and core libraries. Node is powerful, but the power of the Node ecosystem is the thousands of user-contributed libraries. If you want additional libraries and tools, you use `npm` for that. -So why `nvm`? Your operating system typically has one supported version of a programming language environment. So when developers want you to use any other version but the one installed in your operating system, you can't install these packages with `npm` because you have the wrong version of Node. With `nvm`, you have the power and flexibility to run many different versions of the Node platform simultaneously: for development, for testing, for daily use, the way you see fit. +So why `nvm`? Your operating system typically has one supported version of a programming language environment. So when developers want you to use any other version but the one installed in your operating system, you can't install these packages with `npm` because you have the wrong version of Node. With `nvm`, you have the power and flexibility to run many different versions of the Node platform simultaneously: for development, for testing, for daily use, the way you see fit. ## Installation