Node.js virtual environment builder
Project description
Node.js virtual environment
nodeenv (node.js virtual environment) is a tool to create isolated node.js environments.
It creates an environment that has its own installation directories, that doesn’t share libraries with other node.js virtual environments.
Also the new environment can be integrated with the environment which was built by virtualenv (python).
If you use nodeenv feel free to add your project on wiki: Who-Uses-Nodeenv.
Install
Global installation
You can install nodeenv globally with easy_install:
$ sudo easy_install nodeenv
or with pip:
$ sudo pip install nodeenv
or on Debian using dpkg:
$ ln -s debian-upstream debian $ dpkg-buildpackage -uc -us -b $ sudo dpkg -i $(ls -1rt ../nodeenv_*.deb | tail -n1)
Local installation
If you’re using virtualenv then you can install nodeenv via pip/easy_install inside any virtual environment built with virtualenv:
$ virtualenv env $ . env/bin/activate (env) $ pip install nodeenv (env) $ nodeenv --version 0.6.5
If you want to work with the latest version of the nodeenv you can install it from the github repository:
$ git clone https://github.com/ekalinin/nodeenv.git $ ./nodeenv/nodeenv.py --help
or with pip:
$ pip install -e git+https://github.com/ekalinin/nodeenv.git#egg=nodeenv
Dependency
For nodeenv
python (2.6+, 3.3+, or pypy)
make
tail
For node.js
libssl-dev
Usage
Basic
Create new environment:
$ nodeenv env
Activate new environment:
$ . env/bin/activate
Check versions of main packages:
(env) $ node -v v0.10.26 (env) $ npm -v 1.4.3
Deactivate environment:
(env) $ deactivate_node
Advanced
Get available node.js versions:
$ nodeenv --list 0.0.1 0.0.2 0.0.3 0.0.4 0.0.5 0.0.6 0.1.0 0.1.2 0.1.3 0.1.4 0.1.5 0.1.6 0.1.7 0.1.8 0.1.10 0.1.11 0.1.12 0.1.13 0.1.14 0.1.15 0.1.16 0.1.18 0.1.19 0.1.20 0.1.21 0.1.22 0.1.23 0.1.24 0.1.26 0.1.27 0.1.28 0.1.29 0.1.30 0.1.31 0.1.32 0.1.90 0.1.91 0.1.92 0.1.93 0.1.94 0.1.95 0.1.96 0.1.98 0.1.99 0.1.100 0.1.101 0.1.102 0.1.103 0.1.104 0.2.1 0.2.2 0.2.3 0.2.4 0.2.5 0.2.6 0.3.0 0.3.2 0.3.3 0.3.4 0.3.5 0.3.6 0.3.7 0.3.8 0.4.1 0.4.2 0.4.3 0.4.4 0.4.5 0.4.6
Install node.js “0.4.3” without ssl support with 4 parallel commands for compilation and npm.js “0.3.17”:
$ nodeenv --without-ssl --node=0.4.3 --npm=0.3.17 --jobs=4 env-4.3
Install node.js from the source:
$ nodeenv --node=0.10.25 --source env-0.10.25
It’s much faster to install from the prebuilt package than Install & compile node.js from source:
$ time nodeenv --node=0.10.25 --prebuilt env-0.10.25-prebuilt + Install node.js (0.10.25) ... done. real 0m6.928s user 0m0.408s sys 0m1.144s $ time nodeenv --node=0.10.25 --source env-0.10.25-src + Install node.js (0.10.25) ... done. real 4m12.602s user 6m34.112s sys 0m30.524s
Create a new environment with the system-wide node.js:
$ nodeenv --node=system
Saving the versions of all installed packages to a file:
$ . env-4.3/bin/activate (env-4.3)$ npm install -g express (env-4.3)$ npm install -g jade (env-4.3)$ freeze ../prod-requirements.txt
If you want to list locally installed packages use -l option:
(env-4.3)$ freeze -l ../prod-requirements.txt
Create an environment from a requirements file:
$ nodeenv --requirements=../prod-requirements.txt --jobs=4 env-copy
Requirements files are plain text files that contain a list of packages to be installed. These text files allow you to create repeatable installations. Requirements file example:
$ cat ../prod-requirements.txt connect@1.3.0 express@2.2.2 jade@0.10.4 mime@1.2.1 npm@0.3.17 qs@0.0.7
If you already have the python virtualenv tool, and want to use nodeenv and virtualenv in conjunction, then you should create (or activate) the python virtual environment:
# in case of using virtualenv_wrapper $ mkvirtualenv my_env # in case of using virtualenv $ . my_env/bin/activate
and add a node virtual environment to this existing new_venv:
$ nodeenv -p
If you need to set the path to make used to build node:
$ nodeenv -m /usr/local/bin/gmake ENV
That’s all. Now, all your node.js modules will be installed into your virtual environment:
$ workon my_env $ npm install -g coffee-script $ which coffee /home/monty/virtualenvs/my_env/bin/coffee
If environment’s directory already exists then you can use --force option:
$ nodeenv --requirements=requirements.txt --jobs=4 --force env
If you already have an environment and want to update packages from requirements file you can use --update option:
$ . env-4.3/bin/activate (env-4.3)$ nodeenv --requirements=requirements.txt --update env-4.3
If you want to call node from environment without activation then you should use shim script:
$ ./env-4.3/bin/shim --version v0.4.3
If you want to install iojs instead of nodejs then use --iojs:
$ virtualenv env $ . env/bin/activate (env) $ nodeenv --iojs --list 1.0.0 1.0.1 (env) $ nodeenv --iojs -p --prebuilt * Install iojs (1.0.1) ... done. * Appending data to ~/tmp/env/bin/activate
Configuration
You can use the INI-style file ~/.nodeenvrc to set default values for many options, the keys in that file are the long command-line option names.
These are the available options and their defaults:
[nodeenv] debug = False jobs = 2 make = make node = latest npm = latest prebuilt = False profile = False with_npm = False without_ssl = False
Alternatives
There are several alternatives that create isolated environments:
nave - Virtual Environments for Node. Nave stores all environments in one directory ~/.nave. Can create per node version environments using nave use envname versionname. Can not pass additional arguments into configure (for example –without-ssl) Can’t run on windows because it relies on bash.
nvm - Node Version Manager. It is necessarily to do nvm sync for caching available node.js version. Can not pass additional arguments into configure (for example –without-ssl)
virtualenv - Virtual Python Environment builder. For python only.
LICENSE
BSD / LICENSE
Nodeenv changelog
Version 1.3.1
Version 1.3.0
Version 1.2.0
Version 1.1.4
Fixed directory copy #188
Version 1.1.3
Fixed spaces in paths #187
Version 1.1.2
Fixed MANIFEST.in #184
Version 1.1.1
Version 1.1.0
Windows support
Version 1.0.0
Version 0.13.6
Use https for nodejs.org. See # 129
Version 0.13.5
Improved user-agent identification
Version 0.13.4
Version 0.13.3
Version 0.13.2
Fixed freeze command. See # 121
Version 0.13.1
Version 0.13.0
Version 0.12.3
Fixed check for installed curl/tar/etc for py3.
Version 0.12.2
Version 0.12.1
Version 0.12.0
Added support for io.js (new option --iojs)
Fixed get_last_stable_node_version for python3
Version 0.11.1
Version 0.11.0
Version 0.10.0
Version 0.9.6
Version 0.9.5
Fixed a few spelling typos in README. See # 74
Fixed example of using –update option in README. See # 74
Improved args passing into shim script. See # 75
Try to find nodejs if used system-wide node as well. See # 76
Added assert if used system-wide node and it wasnt found. See # 76
Added -l option into freeze command. See # 71
Version 0.9.4
Fixed support for python2.6. See # 70
Version 0.9.3
Version 0.9.2
Fixed infinite loop when system-wide node used. See # 67
Version 0.9.1
Fixed ‘shim’ script if used system-wide node
Fixed shebang in the ‘shim’
Added shim with name ‘node’ in case of using system-wide node
Version 0.9.0
Added shim script. See # 59
Version 0.8.2
Version 0.8.1
Fixed system’s node usage. See # 62
Version 0.8.0
Version 0.7.3
Version 0.7.2
Bug fixing in freeze. See # 47
Version 0.7.1
Added --make option
Version 0.7.0
Version 0.6.6
Version 0.6.5
Node’s source not loaded if it already exists in FS.
Version 0.6.4
Added python3 compatibility. See # 32
Version 0.6.3
Fixed nodeenv -p. See issue # 31
Version 0.6.2
Version 0.6.1
Used pkg_resources.parse_version to compare versions. See pull # 29
Fixed doubling prompt inside a virtualenv. See issues # 26
Version 0.6.0
Version 0.5.3
Bug fix. Used https, /dist/latest/. See pull # 16
Version 0.5.2
Improved installation logic for release candidate versions. See pull # 10
Version 0.5.1
Improved logic for the option ‘–without-npm’. See issue # 14, pull # 15
Version 0.5.0
The virtual environment’s path is no longer hardcoded into the activation script. See pull # 13
Version 0.4.3
Fixed metavar for --npm
npm install -g used for npm >=1.0, not noly for latest
Version 0.4.2
Added README.ru.rst
Version 0.4.1
Fixed bug in print_node_versions. See pull # 11
Added deps in README
Version 0.4.0
Version 0.3.10
Fixed bug in url detection for node.js download
Version 0.3.9
Version 0.3.8
Added NODE_PATH variable export (for correct module search after installation via npm)
Version 0.3.7
Shows command output when error occurs
Excluded ‘npm’ from freeze list
Fixed bug with ‘not only letter’ names in freeze list
Added global installation for npm >= 1.0 (when install soft from requirement file)
Version 0.3.6
Fixed freeze output command. See request # 5
Diagnostic message fixed. See pull # 4
Version 0.3.5
Added option --npm to install certain npm.js version. Request .
Fixed freeze command for npm >= 1.0.x.
Version 0.3.4
Fixed problem #2 with new npm installation script. Added --no-npm-clean option. The default to the npm 0.x cleanup.
Version 0.3.3
Fixed problem #1 with installation from PyPI via easy_install. Added MANIFEST.in file.
Version 0.3.2
Internal improvements
Logging refactoring
Version 0.3.1
Default environment promt is folder name
Version 0.3.0
Renamed nve to nodeenv
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for nodeenv-1.3.4-py2.py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | 561057acd4ae3809e665a9aaaf214afff110bbb6a6d5c8a96121aea6878408b3 |
|
MD5 | 0d10d4ad82fba3c0bc6e24de3c445729 |
|
BLAKE2b-256 | 18042683fe139a9be4d5df02e696f2ed0318ded368feb9e9bbe581611c47e337 |