A Node version manager for the windows folks out there. Inspired by n.

> nodist 0.10
0.10.26

> node -v
v0.10.26

> nodist ls
  0.10.24
  0.10.25
> 0.10.26
  0.11.11
  0.11.12

Don't install node beforehand! Nodist was designed to replace any existing node.js installation, so if node is already installed on your machine, uninstall it first.

1. Put the contents of zip in a directory for use or run git clone git://github.com/marcelklehr/nodist.git. (Note: Certain paths, such as Program Files, requires admin rights for nodist to work.)

2. Add nodist to your system's path: setx /M PATH "path\to\nodist\bin;%PATH%" (setx not available?)

3. Now, run nodist update, which will install the dependencies.

1. Install chocolatey: http://chocolatey.org/

2. Run cinst nodist -Pre

Note: Our chocolatey package has a limitation such that a reboot is required aftewards for nodist to be accessible. We'll try to fix this soon.

1. Remove <..path..>\nodist\bin from your path. (how?).

2. Delete the nodist directory

Nodist understands version patterns, like 0.8 or 0.8.x or ~0.8 as well as 0.8.12 or v0.8.12. As an added bonus, you may also use latest and stable.

Btw, nodist also works in your PowerShell, but you might first need to 'Unblock' the file \bin\nodist.ps1.

All commands implicitly install the specified version before using it, if it isn't installed already.

nodist 0.8.1

Activate the specified version globally.
All subsequent calls of node in any environment will use this version.

nodist ls

This lists all installed versions and highlights the current active one.

nodist dist

This lists all available node versions.

nodist use v0.7.12

Temporarily adds the specified version to the current Path, so all subsequent calls to node in the current terminal environment use that version.
This doesn't have any effects on the globally activated version -- closing the current terminal window will cause nodist to forget the set version.

call nodist use 0.7.12

Use this in a batch script.

nodist r v0.8.1 -- foo.js -s

Use this to run a specific node version, regardless of the globally activated one. Everything after -- will be passed to node.

nodist + v0.8.1

Just checks, if the version is installed and downloads it if not. You usually won't need this.

nodist + all

Install everything. Get yourself a cuppa in the meantime.

nodist - 0.5.10

Removes a version.

nodist --help

Displays a complete list of commands with examples.

set HTTP_PROXY=http://myproxy.com:8213

Set a proxy to use for fetching the executables (you can also use HTTP_PROXY/http_proxy/HTTPS_PROXY/https_proxy).

set NODIST_X64=0

Override x64 auto-detection. Set to 1 to deal with the 64bit versions of node, or to 0 to deal with the 32bit versions.

File an issue and tell me what you'd change or add or what doesn't work for you. Every issue is welcome!

nodist stores your node executables in path\to\nodist\v\, so it can see what's installed and activate previously installed versions.
When a version is activated globally, nodist copies it from nodist\v\<version>\node.exe to nodist\bin\node.exe. 64bit versions are stored in a separate directory called \v-x64. You can alter the path where versions are stored (default: path/to/nodist) using the NODIST_PREFIX env variable.

nodist comes with the latest npm version and will use this all the time, regardless of the node version you have installed.

As the global node version will be subject to change, nodist comes with its own node version and command line files.

Btw, nodist also works in your PowerShell!

Copyright (c) 2012-2013 by Marcel Klehr
MIT License

v0.4.7

• Update bundled npm to v1.4.6 and check-in all files

v0.4.6

• Update pre-packaged npm to v1.4.3

v0.4.5

• Fix nodist -v in powershell (thanks to @devert for reporting)

v0.4.4

• Fix GOTO in batch file (thanks to @BergWerkGIS)

v0.4.3

• Fix a type coercion catch in x64 detection (NODIST_X64=0 had the same effect as NODIST_X64=1; thanks to @springmeyer for reporting)

v0.4.2

• Use the right URI for fetching the x64 executables

v0.4.1

• x64 auto-detection

v0.4.0

• Refactor 64bit support (All commands now work with x64 versions)
• Make npm use the user-chosen node version (thanks to @k-j-kleist for reporting)
• Fix some minor bugs in error handling
• Don't try installing 'vUpdate' after running nodist update
• Install latest stable version after running nodist update

v0.3.11

• Fix 'use' command in powershell (thanks to @paulbatum for reporting)

v0.3.10

• Fix 'use' by fixing 'path' and 'bin' commands

v0.3.9

• Fix renaming mistake (thanks to @paulbatum for reporting)
• Tighten nodist update

v0.3.8

• Add support for x64 versions (thanks to @CycoPH)
• Improve performance by caching version lists

v0.3.7

• Fix nodist run and list commands
• Allow people to use an http proxy (thanks to @gratex)

v0.3.5

• Fix install script. How did that go astray?

v0.3.4

• Fix error message if n.checkout fails

v0.3.3

• Fix installer (thanks to @Ciantic for reporting)
• Fix a bug introduced by npm update

v0.3.2

• Update npm on install/update

v0.3.1

• Optimized nodist + all
• Use a clean npm
• Don't bundle dependencies, anymore -- nodist update must be run at install

v0.3.0

• Dropped optimist (caused more problems than it solved)
• Using node-semver, now, for better usability... (fixes #10)
• Allow use of version patterns for every command (fixes #9)
• Fix issue #8: Version patterns should require internet access

v0.2.8

• Fix use command

v0.2.7

• Deploy by copying node.exe, again, this should allow people to use nodist together with nodemon

v0.2.6

• Fix a bug, that used to break everything on Win7 x64

v0.2.5

• Updated npm to v1.1.48

v0.2.4

• Fix nodist update command to work from all drives
• Add basic support for MinGW shell (thanks to jdiamond) (update and use commands are still missing)
• Fix tests
• Allow npm updates with npm u npm -g
• updated npm

v0.2.3

• Install latest stable as default version
• Add update command
• Updated npm