NVM 1.2.2 – Transform Your PC in Just a Few Clicks with Windows.

Download NVM 1.2.2

Images

Get NVM 1.2.2

All Checks hold Passing

3 Passing Tests

Show Checks Show Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections located in any package files

Details

Generic
Worker
Ansible
PS DSC

Blend to Script Builder Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

Install
Strengthen
Uninstall

To install NVM, zoom the following command from an command line or from PowerShell:

To upgrade NVM, run the following command as a result of the command line or from PowerShell:

To uninstall NVM, run the following command from the command border or from PowerShell:

Deployment Method:

1. Enter A person's Interior Safe Url

(this have to notice similar to https://community.chocolatey.org/api/v2/)

2. Setup The client's Environment

1. Ensure you are unit for management-related deployment

Please see the planning deployment guide

You can also only just receive its package and push it to a repository Download

Method 2: Internalized Package (Reliable, Scalable)

Free Source
- Download the package:
  Download
- Follow manual internalization instructions
Package Internalizer (C4B)
- Run: (additional options) choco transfer nvm --internalize --source=https://community.chocolatey.org/api/v2/
- For package furthermore dependencies run: choco move --source="'INTERNAL REPO URL'"
- Automate package internalization

3. Copy Everybody's Script

choco upgrade nvm -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

If she do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade nvm -y --source="'INTERNAL REPO URL'" $exitCode = $LASTEXITCODE Write-Verbose "Exit code was $exitCode" $validExitCodes = @(0, 1605, 1614, 1641, 3010) assuming ($validExitCodes -contains $exitCode) { Exit 0 } Egress $exitCode - name: Install nvm win_chocolatey: name: nvm version: '1.2.2' provider: INTERNAL REPO URL state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

chocolatey_package 'nvm' do conduct :install source 'INTERNAL REPO URL' version '1.2.2' end

See scripts at https://docs.chef.io/resource_chocolatey_package.html.

cChocoPackageInstaller nvm { Name = "nvm" Version = "1.2.2" Input = "INTERNAL REPO URL" }

Requires cChoco NOTE Resource. Scan docs at https://github.com/chocolatey/cChoco.

MEMO

This package exists likely a meta/virtual (*) or an setup professional (*.install) or compact (*.portable) module package.

Meta/virtual (*) - has a dependency on every *.install or the *.portable package - it is provided by reason of discoverability and as other packages to take a dependency on.
Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated denoting convention)) - usually zips or data the ones require no administrative right to install.
Install (*.install/*.app (deprecated naming convention)) - uses native program setup files, usually requires administrative access to install.

Learn more about chocolatey's gradation linked to executed versus collapsible platforms and/or explore about this kind of package.

Package Approved

This package felt consented by moderator Windos on 04 Feb 2025.

Description NVM

Overview

Manage multiple installations of node.js on a Windows computer.

This has always been a node version manager, barely an io.js manager, so there is don’t think so back-support for io.js. Unit 4+ amounts supported. Remember following running nvm install or nvm use, Windows usually requires administrative rights (to develop symlinks).

There are situations where the ability to switch between different versions of Node.js can be very useful. For example, if you crave to test unique module you're developing having the fresh bleeding extremity version without unhooking the solid version of node, this utility can help.

Usage

nvm-windows runs throughout notable Admin shell. You'll need to start powershell or Command Prompt as Administrator by means of use nvm-windows

NVM for Windows is specific rule line tool. Simply type nvm underneath the panel for help. The basic commands are:

nvm arch [32|64]: Show so long as node is careering in 32 possibly 64 bit mode. Specify 32 or 64 to defeat the default state architecture.
nvm current: Display active version.
nvm install ﹤version﹥ [arch]: The version can be a specific version, "latest" for the latest current version, or "lts" for the most recent LTS version. Optionally specify whether to install the 32 or 64 speck version (defaults to configuration arch). Set [arch] to "all" to install 32 AND 64 bit versions. Add --insecure regarding the end of this command to bypass SSL validation of the remote save server.
nvm list [available]: Plan the node.js installations. Type available at the end to show a list of versions available for download.
nvm on: Enable node.js release candidate management.
nvm off: Disable node.js version management (does not uninstall anything).
nvm proxy [url]: Set an proxy with use for uploads. Leave [url] blank to see the operative proxy. Set [url] to "none" in order to dismiss our proxy.
nvm uninstall ﹤version﹥: Unload a specific version.
nvm use ﹤version﹥ [arch]: Switch to use the specified model. Optionally operate latest, lts, or newest. newest is the latest installed version. Optionally specify 32/64bit architecture. nvm use ﹤arch﹥ has the intention to persevere using the selected version, but replace to 32/64 ounce means. For information about using use within the bounds of notable specific directory (or using .nvmrc), please refer to issue #16.
nvm root ﹤path﹥: Set the directory where nvm can store different designs of node.js. If ﹤path﹥ is not set, the current root will be displayed.
nvm version: Displays each current running version related to NVM for Windows.
nvm node_mirror ﹤node_mirror_url﹥: Batch the node mirror.
nvm npm_mirror ﹤npm_mirror_url﹥: Collection the npm mirror.

Files Virus Scan Results

nvm.1.2.2.nupkg (530033ca9b5b) - ## / 66

In applications where actual malware is found, the packages are subject to removal. Service sometimes has contradictory positives. Moderators do not invariably uphold the preservation of the underlying software, on this occasion that certain package accesses software from the official distribution point and/or validate embedded software against official circulation point (where distribution rights clear redistribution).

Version History Add to Builder Version Downloads Foremost Updated Status NVM 1.2.2 27631 End of the workweek, January 17, 2025 Approved NVM 1.1.12 132106 Second weekday, November 28, 2023 Approved NVM 1.1.9 192764 Tuesday, March 22, 2022 Approved NVM 1.1.5 269636 Monday, Peak summer 26, 2017 Approved NVM 1.1.1 4215 Tuesday, December 20, 2016 Approved Copyright

Release Notes

https://github.com/coreybutler/nvm-windows/releases/latest

Dependencies

- nvm.install (≥ 1.2.2)

Discussion for the NVM Package">Discussion for the NVM Package

Ground Rules:

This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.

Tell us what you love about the crate or NVM, or present us what needs improvement.

Share your experiences with the package, in other words extra configuration or gotchas that you've found.