nenv: A Portable, Per-Project Node.js Runtime for Windows

nenv is a new open-source tool designed to manage Node.js versions on a per-project basis for Windows, addressing common version conflicts and installation restrictions. The tool downloads and isolates a specific Node.js runtime directly into each project folder, enabling developers to work seamlessly across projects with differing Node.js requirements.

Why This Matters

Traditional Node.js version management on Windows often requires global installations and administrator privileges, leading to conflicts and inconsistencies between projects. This can cause build failures, runtime errors, and significant debugging overhead, potentially costing development teams valuable time and resources. nenv aims to resolve these issues by providing a self-contained, portable solution.

Key Insights

Node.js version conflicts are common: Many developers experience issues due to differing Node.js version requirements across projects.
.venv inspiration: nenv mirrors the functionality of Python’s .venv for creating isolated environments.
No admin rights needed: nenv operates without requiring administrator privileges, making it ideal for restricted environments.

Working Example

# Installation
Invoke-WebRequest -Uri "https://cdn.jsdelivr.net/gh/tabreezsajjad/[email protected]/nenv.txt" -OutFile "nenv.cmd"

# Initialization (select Node version, e.g., 20.11.1)
.\nenv.cmd init

# Check Node version
.\nenv.cmd node --version

# Install dependencies
.\nenv.cmd npm install

# Run scripts
.\nenv.cmd dev

Practical Applications

Corporate Laptops: Enables developers to work on multiple Node.js projects on corporate laptops without requiring global installations.
CI/CD Pipelines: Ensures consistent Node.js versions across development, testing, and production environments, preventing “works on my machine” issues.

References:

On This Page

nenv: A Portable, Per-Project Node.js Runtime for Windows