149

I've searched the wiki modules page, but I can't find anything similar to virtualenv (python) or rvm.

Anyone here separates node.js in their own env? I really don't like to install npm system-wide.

Federico Gentile
  • 4,003
  • 7
  • 33
  • 74
Frangossauro
  • 3,636
  • 4
  • 20
  • 14

7 Answers7

190

nodeenv - virtual environment for node.js ( Analog virtualenv )

shorrty
  • 2,183
  • 2
  • 15
  • 9
  • This did look great at start, but I was not able to get npm installation done with nodeenv at the same time with node.js is compiled (on osx Lion). Probably I just could have use nvm install and install npm separately for each nodeenv... by the time I thought of trying it I had multiple node versions already done with other means. – Mikael Lepistö Mar 13 '12 at 03:16
  • 3
    Can be used to install _within_ an existing Python virtual environment, so that the `node.js` environment is activated along with the Python environment. See [`nodeenv -p`](https://github.com/ekalinin/nodeenv). – naitsirhc Jun 01 '14 at 11:53
  • 3
    nodeenv(actually virtualenv+nodeenv) is also fits for fish-shell users since nave and others doesn't support any other shells than bash and zsh. – akarca Oct 30 '14 at 09:39
  • 1
    Is there also a virtualenv-wrapper equivalent for it? – vmonteco Feb 28 '18 at 00:00
  • how exactly is this needed, doesn't npm install the listed versions (from package.json) in your project's node modules' folder by default? or at least doesn't it have an option to do so? Isn't this separate enough? I wonder if there realy is need for me to install another 3rd party tool... – tikej Jan 12 '21 at 09:01
49

If having system wide npm packages is your main issue, then maybe consider using the very cool 'bundle' command with npm. This is closer to freezing gems or using bundler in rails, rather than rvm.

It's super easy. Just create a package.json file:

{ "name": "yourapp", "version": "0.0.1", "dependencies": {"jade": "0.4.1"}}

and then run:

npm bundle vendor

or if your npm version is >= 1.0 run:

npm install

to freeze into the vendor directory. and then use:

require.paths.unshift('./vendor');
bjornd
  • 20,786
  • 4
  • 51
  • 70
bxjx
  • 1,708
  • 15
  • 10
26

There are also some Node version management systems that can help.

Check out Nave https://github.com/isaacs/nave

NVM could also be used https://github.com/creationix/nvm

There is also one called n https://github.com/visionmedia/n

Epeli
  • 16,564
  • 10
  • 63
  • 76
  • 1
    Nvm works great if you just like to have various versions of node.js and npm installed at the same time. For the rest I found it enough to have required modules being installed to project directory with npm. – Mikael Lepistö Mar 13 '12 at 03:11
  • 2
    If you're looking at `nvm` or `n` and want automatic switching when you change directories, look at `avn`: https://github.com/wbyoung/avn – wbyoung May 11 '15 at 21:53
  • 1
    As far as I see n is not a virtual environment. It sill shares all globally installed libraries but npm. – Yannic Hamann Apr 30 '19 at 03:01
8

bxjx's answer is conceptually accurate. However, please note that the bundle command no longer takes a directory. It always drops packages into the node_modules folder, so that npm knows where to find them later (and can avoid double-installing dependencies).

Any solution will probably involve installing npm and nave "system-wide" (that is, in your PATH, which could be in ~ somewhere), but then only installing your specific dependencies in the virtual environment.

I responded more thoroughly on the github issue.

tl;dr: The use case is valid and helpful, and while it's mostly there, it's not as well served as it could be. We should make sure to think it through and do it right.

isaacs
  • 15,487
  • 5
  • 39
  • 31
5

You don't always need to install dependencies globally. Usually it's recommended because then you can use the commands an npm packages provides, but if you install it locally (in the node_modules) directory, you can also use these commands, they only wind up in the node_modules/.bin/ directory, so you'll have to type node_modules/.bin/<command>, which is annoying, but you can of course add this path to your PATH environment variable:

export PATH=node_modules/.bin:$PATH

Then you can just type <command> and it works!

There's actually an npm command that returns an absolute path to the .bin directory:

$ npm bin
/path/to/node_modules/.bin

This command also works when you're in a subdirectory of the project, it will return the first node_modules/.bin directory it finds in it's parent directories.

You can add this alias in your .bashrc to automatically add the .bin/ directory to your PATH:

alias nodebin='export PATH=$(npm bin):$PATH'

So when you're in a directory of a project that has a node_modules/ directory in the root, you can type nodebin and then you can use all the commands that are in the .bin/ directory!

gitaarik
  • 31,690
  • 11
  • 86
  • 92
3

looks there is a better way:

Installing Node.js and npm into a Python Virtualenv

now I can use node tools without mess the global bin environment

Gohan
  • 2,313
  • 2
  • 23
  • 43
2

If you like it simple, I truely recommend visionmedia's n, could not be easier!

https://github.com/visionmedia/n

Lars C. Magnusson
  • 241
  • 2
  • 11