Package Health Score

86 / 100

security
No known security issues
popularity
Key ecosystem project
maintenance
Healthy
community
Sustainable

Explore Similar Packages

Popularity

Key ecosystem project

GitHub Stars: 1.71K
Forks: 210
Contributors: 90

Direct Usage Popularity

Based on project statistics from the GitHub repository for the PyPI package nodeenv, we found that it has been starred 1,710 times.

Security

No known security issues

Security and license risk for latest version

Release Date: Jun 4, 2024
Direct Vulnerabilities: 0
C
0
H
0
M
0
L
Indirect Vulnerabilities: 0
C
0
H
0
M
0
L
License Risk: 0
H
0
M
0
L

All security vulnerabilities belong to production dependencies of direct and indirect packages.

License

BSD-2-Clause

Security Policy

We found a way for you to contribute to the project! Looks like nodeenv is missing a security policy.

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

Keep your project free of vulnerabilities with Snyk

Maintenance

Healthy

Commit Frequency

Open Issues: 55
Open PR: 4
Last Release: 7 months ago
Last Commit: 4 months ago

Further analysis of the maintenance status of nodeenv based on released PyPI versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that nodeenv demonstrates a positive version release cadence with at least one new version released in the past 12 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

Sustainable

Readme: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 90
Funding: No

With more than 10 contributors for the nodeenv repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like nodeenv is missing a Code of Conduct.

Embed Package Health Score Badge

Keep your project healthy

Check your requirements.txt

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Python Versions Compatibility: !=3.0.*,!=3.1.*,!=3.2.*,!=3.3.*,!=3.4.*,!=3.5.*,!=3.6.*,>=2.7

Age: 14 years
Latest Release: 7 months ago
Dependencies: N/A
Versions: 74
Maintainers: 1
Wheels: OS Independent

Readme

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.

local

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.5+, 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 --with-npm --jobs=4 env-4.3

Install node.js from the source:

$ nodeenv --node=0.10.25 --source env-0.10.25

Install node.js from a mirror:

$ nodeenv --node=10.19.0 --mirror=https://npm.taobao.org/mirrors/node

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
$ command -v coffee
/home/monty/virtualenvs/my_env/bin/coffee

Creating a virtual environment with a custom prompt:

> $ nodeenv --node=12.18.2 --prompt="(myenv)" nodeenv

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

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]
node = 'latest'
npm = 'latest'
with_npm = False
jobs = '2'
without_ssl = False
debug = False
profile = False
make = 'make'
prebuilt = True
ignore_ssl_certs = False
mirror = None

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

Windows related fix #207
Fixed url for arm64 #210
Fixed fish support #212

Version 1.3.0

Fixed symlink creation #189
Python3.6 support #200
Added activate for fish #201
Fixed cp866 #202
Added Conda support #203

Version 1.2.0

Support for Cygwin #194 #195
tox.ini as default configuration file #197

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

Improve Windows support. See #181
Fix bug when downgrading using --force. See #183
Environment creation fails with non-ASCII chars in path. See #49

Version 1.1.0

Windows support

Version 1.0.0

--prebuilt is default. See # 161
Added --source option
Added support for the ARM. See # 171
Fixed issue with $PATH. See # 86

Version 0.13.6

Use https for nodejs.org. See # 129

Version 0.13.5

Improved user-agent identification

Version 0.13.4

Custom user-agent. See # 125, # 127

Version 0.13.3

Fixed env creation with non-ASCII chars in path. See # 49
Fixed logging with unicode chars. See # 96
Skip new lines at the end of requirements.txt. See # 122
Fixed UnicodeDecodeError at build on non UTF-8 environment. See # 124

Version 0.13.2

Fixed freeze command. See # 121

Version 0.13.1

Fixed bug: nodeenv --list is raising TypeError. See # 117, # 118

Version 0.13.0

Removed deps from sort, egrep, curl, tar. See # 114, # 116.

Version 0.12.3

Fixed check for installed curl/tar/etc for py3.

Version 0.12.2

Added check for installed curl/egrep/sort/tar. See # 110, # 61

Version 0.12.1

Removed dep for lxml in favor of stdlib HTMLParser. See # 109
Added integration with travis-ci. See # 109
Added some tests. See # 109

Version 0.12.0

Added support for io.js (new option --iojs)
Fixed get_last_stable_node_version for python3

Version 0.11.1

Disallow prefix overridden by .npmrc. See # 98, # 100, # 103

Version 0.11.0

Improved dpkg rules. See # 90
Added --config-file option. See # 91
Read "./setup.cfg" in addition to "~/.nodeenvrc" by default. See # 91
Python3 compatibility. See # 92, # 93

Version 0.10.0

Added support for config file. See # 85
Using of virtualenv detected via python not env variable. See # 87
Fixed freeze for zsh. See # 88
Added nodejs symlink creation. See # 84

Version 0.9.6

Removed os.symlink added in # 76. See # 84

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

Fixed npm when using prebuilt binaries on Mac OS X. See # 68
Fixed using system node under python3.4. See # 43
If used system node script bin/node always overwritten

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

Fixed prebuilt installation:
- cp more choosy. See # 64
- exclude top-level files in prebuilt tar. See # 63

Version 0.8.1

Fixed system's node usage. See # 62

Version 0.8.0

Added support for prebuilt packages. See # 56
Added support for python3. See # 42

Version 0.7.3

Fixed npm.js redirect. See # 52
Added --update option. See # 25

Version 0.7.2

Bug fixing in freeze. See # 47

Version 0.7.1

Added --make option

Version 0.7.0

added --force. See # 37
python3 support (first steps). See # 38, # 39
escaping all directories used by subprocesses. See # 40
added an option to use system-wide node. See # 41

Version 0.6.6

Fixed incomplete package names using freeze. See # 35
Fixed packages installation type in README. See # 33

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

Skipped stand-alone npm installation by default. See pull # 30
--without-npm has been changed to --with-npm. See pull # 30
Fixed options for running Make instances in parallel. See pull # 30

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

Fixed typo in deactive command. See pull # 20
Not used "--insecure" to download npm. See pull # 21
Removed "src" directory after installation. See pull # 22
Added option "--clean-src"
Added integration with python's virtualenv. See pull # 23

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

Compatibility with virtualenv (renamed deactivate to deactivate_node). See pull # 9, issue # 6

Version 0.3.10

Fixed bug in url detection for node.js download

Version 0.3.9

Deleted notify method calls. See pull # 7
Updated tar url for node.js > 0.5.0. See pull # 8

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

FAQs

What is nodeenv?

Node.js virtual environment builder. Visit Snyk Advisor to see a full health score report for nodeenv, including popularity, security, maintenance & community analysis.

Is nodeenv popular?

The python package nodeenv receives a total of 6,087,425 weekly downloads. As such, nodeenv popularity was classified as a key ecosystem project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is nodeenv well maintained?

We found that nodeenv demonstrated a healthy version release cadence and project activity. It has a community of 90 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is nodeenv safe to use?

The python package nodeenv was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 21 December-2024, at 01:52 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP