Master Elegant Multi‑Version Node.js & npm Setup on Windows

I always thought my elegant setup was known, until I saw many peers download the

.msi

to install

node

, which broke my sense of elegance.

.msi Installation

The Windows one‑click installer is the simplest way to install

node

, but it has several drawbacks.

It cannot install multiple

node

versions, and many users need parallel versions.

The installer’s handling of

npm

is opaque; we don’t know which directories are created or how to configure them.

Multiple versions can be managed with tools like

nvm-windows

, but this article focuses on the

npm

-related setup.

Elegant Installation

Directory

Create a dedicated directory on the E: drive to manage

node

and

npm

, for example

E:\NODE

. The structure should be:

<code>E:\NODE\node
E:\NODE\npm-global
E:\NODE\npm-cache
</code>

The

node

folder holds

node.exe

(and can hold multiple versions);

npm-global

is the installation target for

npm i xxx -g

;

npm-cache

stores npm’s cache to avoid repeated downloads.

Download .exe

Download the executable (

.exe

) and place it in the

node

folder. The resulting layout is:

<code>E:/NODE/
    node/
        node.exe
        node-v0.12.0.exe
    npm-global/
    npm-cache/
</code>

You can keep multiple

node

versions and use them from the command line:

<code>node --version
node-v0.12.0 --version
</code>

These commands will fail until the paths

E:\NODE\node

and

E:\NODE\npm-global

are added to the system PATH; configuring the PATH is outside the scope of this article.

npm

Now that

node

works, we set up

npm

.

Install npm

First, manually download the latest

npm

package, extract it into a

node_modules

folder under

npm-global

, and rename the extracted folder to

npm

. The directory now looks like:

<code>E:/NODE/
    node/
    npm-global/
        node_modules/
            npm/
                bin/
                xxx
    npm-cache/
</code>

Copy the

npm

and

npm.cmd

files from the

bin

directory into

npm-global

. After that,

npm --version

should work.

Configure npm directories

Set npm’s prefix and cache to the dedicated folders:

<code>npm config set prefix "E:\NODE\npm-global"
npm config set cache "E:\NODE\npm-cache"
</code>

Now install a global package to test the setup:

<code>npm i -g es-checker
es-checker
</code>

All

node

and

npm

related files are now centralized under

E:\NODE\

, making

npm

transparent and eliminating the black‑box nature of the default installer. The elegant installation method concludes here.