Download NVM 1.2.2 for Windows – No Hassles, Just the Program You Want

Download NVM 1.2.2

UI shots

Get NVM 1.2.2

• 1
• 2
• 3

All Checks are Passing

3 Gliding Tests

Show Checks Show Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Investigating Successful:

No detections found in any grouping files

Details

• Unspecialized
• Individual
• Ansible
• PS DSC

Add to Script Builder Learn More

Deployment Method: Individual Install, Modify, & Uninstall

• Build
• Upgrade
• Uninstall

To install NVM, run particular following command resulting from the suggestion line or originating from PowerShell:

>

To upgrade NVM, run the following command based on the command line or from PowerShell:

>

To uninstall NVM, run the following command from the command line or on account of PowerShell:

>

Deployment Method:

1. Enter Your Internal Repository Url

(this should look similar concerning https://community.chocolatey.org/api/v2/)

2. Installation Your Environment

1. Ensure you are set for administrative deployment

Please see the organizational deployment phase guide

You has the opportunity to as well just get those package and move it before a repository Download

Option 2: Internalized Bag (Reliable, Scalable)

• Open Input

  • Download the package:

    Load
  • Follow manual internalization instructions
• Package Internalizer (C4B)
  • Run: (additional options) choco download nvm –internalize –source=https://community.chocolatey.org/api/v2/
  • For combination and dependencies run: choco push –source="’INTERNAL REPO URL’"
  • Automate package internalization

3. Copy Your Script

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

See options you has permission to clear to upgrade.

See best practices for scripting.

If you do use single PowerShell script, use the underneath to deliver bad egress point 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) if ($validExitCodes -contains $exitCode) { Exit 0 } Exit $exitCode – identity marker: Install nvm win_chocolatey: name: nvm format: ‘1.2.2’ source: INTERNAL REPO URL state: present

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

chocolatey_package ‘nvm’ do action :install source ‘INTERNAL REPO URL’ version ‘1.2.2’ end

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

cChocoPackageInstaller nvm { Name = “nvm” Framework = “1.2.2” Generator = “INTERNAL REPO URL” }

Requires cChoco DSC Provision. See docs along https://github.com/chocolatey/cChoco.

NOTE

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

• Meta/virtual (*) – has a dependency on each *.install otherwise the *.portable offer – matter constitutes provided intended for discoverability equally for other packages by take a dependency on.
• Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) – usually zips or archives that require no administrative access to install.
• Install (*.install/*.app (deprecated dubbed convention)) – uses native installation assistants, usually requires organizational access into install.

Learn more about chocolatey’s distinction of constructed versus portable apps and/or learn about this kind of package.

Delivery Approved

This package was approved 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 framework manager, not an io.js manager, so there is no back-support for io.js. Node 4+ is supported. Remember when running nvm assemble if not nvm use, Windows usually requires administrative justifications (to produce symlinks).

There are issues within which the ability for switch between different versions of Node.js can be very useful. For example, if you want to test particular module you’re developing with each latest bleeding edge edition without uninstalling the stable version of node, this utility can help.

Usage

nvm-windows runs in an Admin shell. You’ll need to start powershell or Command Prompt depending on Administrator to use nvm-windows

NVM for Windows is a recommendation line tool. Simply type nvm in the console for guide. No basic prescriptions are:

• nvm arch [32|64]: Show if node is running in 32 or 64 bit mode. Reveal 32 or 64 to override the default architecture.
• nvm current: Demonstrate busy version.
• nvm integrate ﹤version﹥ [arch]: The version can be a specific version, "latest" for the ultra-modern current version, or "lts" with the purpose of the most recent LTS version. Optionally list whether to install the 32 or 64 bit version (defaults with system arch). Kit [arch] to "all" to install 32 AND 64 bit versions. Impart –insecure to the end of this rule with regard to bypass SSL validation of the remote get server.
• nvm list [available]: List the node.js implementations. Type handy at the end to show selected list of versions available for download.
• nvm on: Enable node.js version management.
• nvm off: Disable node.js version management (does unfit uninstall anything).
• nvm go-between [url]: Set a proxy to use for downloads. Take off [url] blank to see the current proxy. Set [url] to "none" to take out the proxy.
• nvm uninstall ﹤version﹥: Uninstall a targeted version.
• nvm use ﹤version﹥ [arch]: Switch to use the specified version. Optionally use latest, lts, should you prefer newest. newest is some hot-off-the-press installed format. Optionally express 32/64bit architecture. nvm use ﹤arch﹥ will continue using the selected version, but switch to 32/64 bit procedure. For details about using use in a specific inventory (or using .nvmrc), if it’s okay name to issue #16.
• nvm root ﹤path﹥: Set the collection where nvm should store exceptional versions of node.js. If ﹤path﹥ is not set, the modern root will comprise displayed.
• nvm version: Displays the current jogging version of NVM for Windows.
• nvm node_mirror ﹤node_mirror_url﹥: Set the station mirror.
• nvm npm_mirror ﹤npm_mirror_url﹥: Set the npm mirror.

Files Virus Scan Results

Log in or click on link to see number of positives.

• nvm.1.2.2.nupkg (530033ca9b5b) – ## / 66

In cases where unambiguous malware is found, the packages continue subject to detachment. Product partially has deceptive positives. Leaders do not necessarily validate the safety of the underlying software, only that that package retrieves software resulting from the official distribution point and/or validate embedded software against official distributional point (where redistribution rights allow redistribution).

Version History Add by means of Founder Version Downloads Last Updated Status NVM 1.2.2 27920 Friday, January 17, 2025 Approved NVM 1.1.12 132120 Tuesday, November 28, 2023 Approved NVM 1.1.9 192772 Tuesday, March 22, 2022 Agreed NVM 1.1.5 269636 Monday, June 26, 2017 Approved NVM 1.1.1 4216 Tuesday, December 20, 2016 Acknowledged Licensing rights

Copyright (c) 2022 Ecor Projects LLC

Release Details

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

Dependencies

• • nvm.install (≥ 1.2.2)

Discussion for the NVM Package”>Discussion in exchange for the NVM Package

Ground Rules:

This discussion will carry over multiple versions. If the listener maintain a comment about a particular version, please note that among the reader’s comments.

Tell the collective what you love about the package alternatively NVM, alternatively advise us what needs improvement.

Share your experiences with its package, or amplified configuration or gotchas that you’ve found.