nvm-sh / nvm

2010-04-15 · Source: Github Trending: All languages · Field: Technology & Digital — Software Development & Engineering, Cloud Computing & IT Infrastructure · Depth: Intermediate, extended

Summary

Node Version Manager (nvm) is a per-user, per-shell command-line tool designed to install and manage multiple Node.js versions on POSIX-compliant shells across Unix, macOS, and Windows WSL. The current supported version is v0.40.4. Installation typically involves a cURL or Wget script that clones the nvm repository to `~/.nvm` and configures shell profile files like `~/.bashrc`. Users can install specific Node.js versions (e.g., `nvm install 16`), set default versions, manage aliases, and migrate global npm packages between Node.js versions using flags like `--reinstall-packages-from` and `--latest-npm`. Nvm also supports `.nvmrc` files for automatic version switching based on directory context and offers specific installation guidance for Docker environments and Alpine Linux, which requires additional build tools due to its `musl` C/C++ stack.

Key takeaway

For DevOps Engineers managing Node.js environments, nvm streamlines version control, especially in CI/CD pipelines and Docker. You should integrate `.nvmrc` files into project repositories to ensure consistent Node.js versions across development and deployment, reducing "works on my machine" issues. Leverage nvm's `--reinstall-packages-from` and `--latest-npm` flags to simplify package migration when updating Node.js versions, ensuring dependencies remain compatible and up-to-date.

Key insights

Nvm simplifies managing multiple Node.js versions across various development environments and shells.

Principles

• Per-user, per-shell installation
• Configuration via `.nvmrc` files
• LTS version support

Method

Install nvm via a shell script, then use `nvm install <version>` to add Node.js versions. Switch versions with `nvm use <version>` or automatically via `.nvmrc` files in project directories.

In practice

• Use `nvm install node` for the latest Node.js.
• Employ `nvm install --reinstall-packages-from=current 'lts/*'` for LTS.
• Create `.nvmrc` for project-specific Node.js versions.

Topics

• Node Version Manager
• Node.js Versioning
• Shell Integration
• Docker Deployment
• Troubleshooting & Compatibility

Code references

• nvm-sh/logos
• nvm-sh/nvm
• ohmyzsh/ohmyzsh
• coreybutler/nvm-windows
• marcelklehr/nodist

Best for: Software Engineer, DevOps Engineer

Related on AIssential

• pnpm 11 Release Candidate: ESM Distribution, Supply Chain Defaults and a New Store Format — pnpm 11 Release Candidate introduces significant reworks focused on performance, supply chain safety, and a stricter configuration surface, now distributed as pure ESM and requiring Node.js v22 or later.
• How to Orchestrate Across Multiple Databricks Workspaces Without Losing Your Mind — Managing cross-workspace dependencies is critical for scalable Databricks orchestration, which native tools lack.
• Node.js Moves to One Major Release Per Year, Starting with Node 27 — The Node.js project is shifting to one major release per year, with all versions becoming LTS, to ease maintainer burden.
• Vibe DevOps is Already Happening? — Vibe DevOps involves direct SSH access to production for deployments and maintenance, eschewing formal infrastructure-as-code.
• Achieving Peak System and Workload Efficiency on NVIDIA GB200 NVL72 with Slurm Block Scheduling — NVIDIA GB200 NVL72's rack-scale NVLink coherence requires Slurm's topology/block plugin for optimal scheduling.
• Measuring LLMs' Impact on N-day Exploits — LLMs, particularly Claude Mythos Preview, drastically accelerate N-day exploit creation, making patch gaps critically dangerous.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Github Trending: All languages.